public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jorge Eduardo Candelaria <jedu@slimlogic•co.uk>
Cc: Liam Girdwood <lrg@slimlogic•co.uk>,
	linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Graeme Gregory <gg@slimlogic•co.uk>
Subject: Re: linux-next: build failure after merge of the voltage tree
Date: Wed, 11 May 2011 12:27:38 +1000	[thread overview]
Message-ID: <20110511122738.93d239cb.sfr@canb.auug.org.au> (raw)
In-Reply-To: <6B0D58A8-B278-49D6-835F-C38E7517FCD5@slimlogic.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1993 bytes --]

Hi Jorge,

On Tue, 10 May 2011 12:30:36 -0500 Jorge Eduardo Candelaria <jedu@slimlogic•co.uk> wrote:
>
> On May 10, 2011, at 3:38 AM, Liam Girdwood wrote:
> 
> > On Tue, 2011-05-10 at 12:44 +1000, Stephen Rothwell wrote:
> >> Hi Liam,
> >> 
> >> After merging the voltage tree, today's linux-next build (x86_64
> >> allmodconfig) failed like this:
> >> 
> >> ERROR: "tps65910_gpio_init" [drivers/mfd/tps65910.ko] undefined!
> >> ERROR: "tps65910_irq_init" [drivers/mfd/tps65910.ko] undefined!
> >> ERROR: "irq_modify_status" [drivers/mfd/tps65910-irq.ko] undefined!
> >> ERROR: "irq_set_chip_and_handler_name" [drivers/mfd/tps65910-irq.ko] undefined!
> >> ERROR: "handle_edge_irq" [drivers/mfd/tps65910-irq.ko] undefined!
> >> 
> >> I have used the voltage tree from next-20110509 for today.
> > 
> > Jorge, could you send a fix for this today.
> 
> The following patch should solve this:
> 
> From: Jorge Eduardo Candelaria <jedu@slimlogic•co.uk>
> MFD: Fix TPS65910 build
> 
> Support for tps65910 as a module is not available. The driver can
> only be compiled as built-in. OTOH, the regulator driver can still
> be built as module without breaking the compilation.
> 
> Signed-off-by: Jorge Eduardo Candelaria <jedu@slimlogic•co.uk>

Today (even with the above patch included) I got these errors from the
x86_64 allmodconfig build:

tps65910.c:(.text+0xf4140): undefined reference to `i2c_master_send'
drivers/built-in.o: In function `tps65910_i2c_read':
tps65910.c:(.text+0xf41d2): undefined reference to `i2c_transfer'
drivers/built-in.o: In function `tps65910_i2c_init':
tps65910.c:(.init.text+0xcb83): undefined reference to `i2c_register_driver'
drivers/built-in.o: In function `tps65910_i2c_exit':
tps65910.c:(.exit.text+0x6e0): undefined reference to `i2c_del_driver'

I have used the voltage tree from next-20110509 again today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

  parent reply	other threads:[~2011-05-11  2:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10  2:44 linux-next: build failure after merge of the voltage tree Stephen Rothwell
2011-05-10  8:38 ` Liam Girdwood
2011-05-10 17:30   ` Jorge Eduardo Candelaria
2011-05-10 19:57     ` Liam Girdwood
2011-05-11  2:27     ` Stephen Rothwell [this message]
2011-05-11  6:43       ` Jorge Eduardo Candelaria
2011-05-11 13:29         ` Liam Girdwood
2011-05-11  8:47       ` [PATCH] mfd: TPS65910 depends on I2C and must be built in Mark Brown
2011-05-11 13:35         ` Liam Girdwood
2011-05-11 13:36           ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2010-12-15  2:09 linux-next: build failure after merge of the voltage tree Stephen Rothwell
2010-12-15  9:04 ` Liam Girdwood
2010-12-15 14:03   ` Mark Brown
2010-12-14  4:49 Stephen Rothwell
2010-12-14  5:10 ` Yong Shen
2010-12-14 15:56   ` Liam Girdwood
2010-12-15  2:03     ` Yong Shen
2010-11-11  0:36 Stephen Rothwell
2010-11-11 11:46 ` Mark Brown
2010-11-11 12:09   ` Liam Girdwood

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110511122738.93d239cb.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=gg@slimlogic$(echo .)co.uk \
    --cc=jedu@slimlogic$(echo .)co.uk \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=lrg@slimlogic$(echo .)co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox