From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
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 21:14:33 +1100 [thread overview]
Message-ID: <20091124211433.cd1b7e96.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20091124095715.GA20505@rakim.wolfsonmicro.main>
[-- Attachment #1: Type: text/plain, Size: 934 bytes --]
Hi Mark,
On Tue, 24 Nov 2009 09:57:16 +0000 Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
>
> 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...
Sorry, I don't have the actual config (as I overwrite my build directory
between each merge). However, if I checkout the mfd tree (alone -
nothing else in linux-next) and do "make ARCH=x86_64 allmodconfig", I get
the following in my .config:
CONFIG_I2C=m
CONFIG_MFD_CORE=m
CONFIG_MFD_WM831X=y
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-11-24 10:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 5:37 Stephen Rothwell
2009-11-24 9:57 ` Mark Brown
2009-11-24 10:14 ` Stephen Rothwell [this message]
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 3:54 ` Stephen Rothwell
2009-10-06 4:19 ` Haojian Zhuang
2009-10-08 5:59 ` Haojian Zhuang
2009-10-12 2:11 ` Stephen Rothwell
[not found] <20090112140318.e25cd2bf.sfr@canb.auug.org.au>
[not found] ` <20090112100753.GA21301@fedora.yogi>
2009-01-13 6:24 ` Stephen Rothwell
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=20091124211433.cd1b7e96.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sameo@linux.intel.com \
/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
all inboxes | Powered by JetHome®