From: Samuel Ortiz <sameo@linux.intel.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: linux-next: Tree for July 25 (mfd/arizona)
Date: Fri, 27 Jul 2012 15:26:34 +0200 [thread overview]
Message-ID: <20120727132634.GN16859@sortiz-mobl> (raw)
In-Reply-To: <501038CF.9090902@xenotime.net>
Hi Randy
On Wed, Jul 25, 2012 at 11:19:59AM -0700, Randy Dunlap wrote:
> On 07/24/2012 09:30 PM, Stephen Rothwell wrote:
>
> > Hi all,
> >
> >
> > Changes since 20120724:
> >
> >
> > The mfd tree gained a conflict against Linus' tree.
>
>
>
> on i386 and x86_64:
>
> CONFIG_MFD_ARIZONA=y
> CONFIG_MFD_ARIZONA_I2C=m
> CONFIG_MFD_CORE=m
>
> drivers/built-in.o: In function `arizona_dev_init':
> (.devinit.text+0x3ab0): undefined reference to `mfd_add_devices'
> drivers/built-in.o: In function `arizona_dev_init':
> (.devinit.text+0x3fdc): undefined reference to `mfd_add_devices'
> drivers/built-in.o: In function `arizona_dev_init':
> (.devinit.text+0x3fff): undefined reference to `mfd_add_devices'
> drivers/built-in.o: In function `arizona_dev_init':
> (.devinit.text+0x4059): undefined reference to `mfd_remove_devices'
> drivers/built-in.o: In function `arizona_dev_exit':
> (.devexit.text+0x9): undefined reference to `mfd_remove_devices'
>
> because MFD_ARIZONA is bool, so builtin, while MFD_CORE=m,
> so the builtin code cannot call the loadable module code.
This is fixed now, by having MFD_ARIZONA selecting MFD_CORE.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2012-07-27 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 4:30 linux-next: Tree for July 25 Stephen Rothwell
2012-07-25 18:19 ` linux-next: Tree for July 25 (mfd/arizona) Randy Dunlap
2012-07-27 13:26 ` Samuel Ortiz [this message]
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=20120727132634.GN16859@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--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).