All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: mfd tree build failure
Date: Tue, 24 Nov 2009 09:57:16 +0000	[thread overview]
Message-ID: <20091124095715.GA20505@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <20091124163753.381d9a83.sfr@canb.auug.org.au>

On Tue, Nov 24, 2009 at 04:37:53PM +1100, Stephen Rothwell wrote:

> drivers/built-in.o: In function `wm831x_i2c_remove':
> wm831x-core.c:(.text+0xd108b): undefined reference to `mfd_remove_devices'
> drivers/built-in.o: In function `wm831x_i2c_write_device':
> wm831x-core.c:(.text+0xd119c): undefined reference to `i2c_master_send'
> drivers/built-in.o: In function `wm831x_i2c_read_device':
> wm831x-core.c:(.text+0xd1208): undefined reference to `i2c_master_send'
> wm831x-core.c:(.text+0xd1237): undefined reference to `i2c_master_recv'

> Caused by commit 4f7231a3ff624ad8a0fdace424b10a8b262071cf ("mfd: Don't
> allow wm831x to be built as a module").  CONFIG_MFD_CORE is "m" and
> CONFIG_I2C is "m" while CONFIG_MFD_WM831X is "y".  "select" is a real
> problem :-(

There's something more seriously wrong than the select with your config
here - the driver depends on (rather than selecting) I2C and you're also
seeing undefined references to the I2C API.  The select on MFD_CORE
should also be forcing that to be built in (it does normally).

Could you please post the actual configuration you're using?  I suspect
some Kbuild bug has been triggered here...

  reply	other threads:[~2009-11-24  9:57 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-24  5:37 linux-next: mfd tree build failure Stephen Rothwell
2009-11-24  9:57 ` Mark Brown [this message]
2009-11-24 10:14   ` Stephen Rothwell
2009-11-24 10:40     ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2010-01-19  4:06 Stephen Rothwell
2010-01-19 10:59 ` Samuel Ortiz
2010-01-19 11:34   ` Stephen Rothwell
2010-01-11  5:02 Stephen Rothwell
2010-01-11 10:51 ` Mark Brown
2010-01-11 12:02   ` Haojian Zhuang
2010-01-11 12:33     ` Samuel Ortiz
2010-01-11 22:44       ` Stephen Rothwell
2009-11-23  3:41 Stephen Rothwell
2009-11-23  4:03 ` Stephen Rothwell
2009-11-23 12:29   ` Samuel Ortiz
2009-11-23 13:11     ` Mark Brown
2009-11-23 14:44       ` Samuel Ortiz
2009-11-23 15:20         ` Mark Brown
2009-11-23  3:35 Stephen Rothwell
2009-11-23 12:26 ` Samuel Ortiz
2009-11-23 16:32   ` Dmitry Torokhov
2009-11-24 23:35     ` Samuel Ortiz
2009-10-06  2:02 Stephen Rothwell
2009-10-06  2:35 ` Haojian Zhuang
2009-10-06  2:35   ` Haojian Zhuang
2009-10-06  3:54   ` Stephen Rothwell
2009-10-06  4:19     ` Haojian Zhuang
2009-10-08  5:59       ` Haojian Zhuang
2009-10-08  5:59         ` Haojian Zhuang
2009-10-12  2:11 ` Stephen Rothwell
2009-01-12  3:03 Stephen Rothwell
2009-01-12 10:07 ` Balaji Rao
2009-01-13  6:24   ` Stephen Rothwell
2009-01-14 12:12   ` Samuel Ortiz
2008-08-05 14:08 Stephen Rothwell
2008-08-05 15:39 ` ian
2008-08-05 16:05   ` Adrian Bunk
2008-08-05 18:50     ` ian
2008-08-05 16:05   ` Stephen Rothwell
2008-08-05 16:08     ` Samuel Ortiz
2008-08-05 16:16       ` Stephen Rothwell
2008-08-05 17:40         ` Samuel Ortiz
2008-08-05 18:46           ` ian
2008-08-06  9:53             ` Samuel Ortiz
2008-08-06  0:40           ` Stephen Rothwell
2008-08-05  5:09 Stephen Rothwell
2008-08-05 13:03 ` ian
2008-08-05 13:09   ` Samuel Ortiz
2008-08-05 13:22     ` Stephen Rothwell
2008-08-05 15:29     ` ian

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=20091124095715.GA20505@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sameo@linux.intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.