linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Jorge Eduardo Candelaria <jedu@slimlogic.co.uk>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	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 14:29:43 +0100	[thread overview]
Message-ID: <1305120583.3277.14.camel@odin> (raw)
In-Reply-To: <9185B06E-E2C4-4F35-8605-9654CA3BA966@slimlogic.co.uk>

On Wed, 2011-05-11 at 01:43 -0500, Jorge Eduardo Candelaria wrote:
> On May 10, 2011, at 9:27 PM, Stephen Rothwell wrote:
> 
> > 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.
> 
> Following patch should fix the dependency problems. Please review:
> 
> From: Jorge Eduardo Candelaria <jedu@slimlogic.co.uk>
> [PATCH] MFD: TPS65910: Fix I2C dependency
> 
> TPS65910 driver can only be compiled built-in, so the I2C driver
> should be as well.
> 
> Signed-off-by: Jorge Eduardo Candelaria <jedu@slimlogic.co.uk>
> ---
>  drivers/mfd/Kconfig |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
> index c78865e..0131d49 100644
> --- a/drivers/mfd/Kconfig
> +++ b/drivers/mfd/Kconfig
> @@ -673,7 +673,7 @@ config MFD_OMAP_USB_HOST
>  
>  config MFD_TPS65910
>  	bool "TPS65910 Power Management chip"
> -	depends on I2C && GPIOLIB
> +	depends on I2C=y && GPIOLIB
>  	select MFD_CORE
>  	help
>  	  if you say yes here you get support for the TPS65910 series of

Now applied.

Liam

  reply	other threads:[~2011-05-11 16:29 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
2011-05-11  6:43       ` Jorge Eduardo Candelaria
2011-05-11 13:29         ` Liam Girdwood [this message]
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=1305120583.3277.14.camel@odin \
    --to=lrg@slimlogic.co.uk \
    --cc=gg@slimlogic.co.uk \
    --cc=jedu@slimlogic.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).