From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Samuel Ortiz <sameo@openedhand•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Haojian Zhuang <haojian.zhuang@marvell•com>,
Mark Brown <broonie@opensource•wolfsonmicro.com>
Subject: Re: linux-next: mfd tree build failure
Date: Mon, 12 Oct 2009 13:11:31 +1100 [thread overview]
Message-ID: <20091012131131.91dccb99.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20091006130202.5e18a332.sfr@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1467 bytes --]
Hi Samuel,
On Tue, 6 Oct 2009 13:02:02 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> drivers/built-in.o: In function `pm8607_write_device':
> 88pm8607.c:(.text+0xd02e9): undefined reference to `i2c_master_send'
> drivers/built-in.o: In function `pm8607_read_device':
> 88pm8607.c:(.text+0xd033b): undefined reference to `i2c_master_send'
> 88pm8607.c:(.text+0xd035c): undefined reference to `i2c_master_recv'
> drivers/built-in.o: In function `pm8607_init':
> 88pm8607.c:(.init.text+0xa9bd): undefined reference to `i2c_register_driver'
> drivers/built-in.o: In function `pm8607_probe':
> 88pm8607.c:(.devinit.text+0x4db6): undefined reference to `mfd_add_devices'
> drivers/built-in.o: In function `pm8607_exit':
> 88pm8607.c:(.exit.text+0x598): undefined reference to `i2c_del_driver'
> drivers/built-in.o: In function `pm8607_remove':
> 88pm8607.c:(.devexit.text+0x198): undefined reference to `mfd_remove_devices'
>
> Obviously caused by commit 9ec6cd8f2235ddeee5b39068956f14238a12a617
> ("mfd: Add 88PM8607 driver").
>
> This build has CONFIG_I2C=m and CONFIG_MFD_CORE=m.
>
> I have used the version of the mfd tree form next-20091005 for today.
This build failure is still happening and I am still using the mfd tree
from next-20091005.
--
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-10-12 2:12 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 2:02 linux-next: mfd tree build failure 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 [this message]
-- 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-24 5:37 Stephen Rothwell
2009-11-24 9:57 ` Mark Brown
2009-11-24 10:14 ` Stephen Rothwell
2009-11-24 10:40 ` Mark Brown
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-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=20091012131131.91dccb99.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=broonie@opensource$(echo .)wolfsonmicro.com \
--cc=haojian.zhuang@marvell$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sameo@openedhand$(echo .)com \
/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