From: Arnd Bergmann <arnd@arndb.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild test robot <fengguang.wu@intel.com>,
kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Randy Dunlap <rdunlap@infradead.org>,
Jonathan Cameron <jic23@kernel.org>
Subject: Re: [mmotm:master 7/197] ak8975.c:undefined reference to `i2c_smbus_write_byte_data'
Date: Thu, 26 Feb 2015 22:23:02 +0100 [thread overview]
Message-ID: <2111473.jxZaFqNM44@wuerfel> (raw)
In-Reply-To: <20150226124432.2220a6bfd14cc9ce154f8a62@linux-foundation.org>
On Thursday 26 February 2015 12:44:32 Andrew Morton wrote:
> On Thu, 26 Feb 2015 15:36:18 +0800 kbuild test robot <fengguang.wu@intel.com> wrote:
>
> > It's probably a bug fix that unveils the link errors.
> >
> > tree: git://git.cmpxchg.org/linux-mmotm.git master
> > head: 87bf5bee8749a1d3c82d12a55a1e33f6a22da8ed
> > commit: 7d789876f1a932dfa1a70ae8eeba270aa34358ad [7/197] rtc: ds1685: fix ds1685_rtc_alarm_irq_enable build error
> > config: i386-randconfig-nexr0-0226 (attached as .config)
> > reproduce:
> > git checkout 7d789876f1a932dfa1a70ae8eeba270aa34358ad
> > # save the attached .config to linux build tree
> > make ARCH=i386
> >
> > All error/warnings:
> >
> > drivers/built-in.o: In function `ak8975_set_mode':
> > >> ak8975.c:(.text+0x16c108): undefined reference to `i2c_smbus_write_byte_data'
> > drivers/built-in.o: In function `ak8975_probe':
> > >> ak8975.c:(.text+0x16c29b): undefined reference to `i2c_smbus_read_i2c_block_data'
> > >> ak8975.c:(.text+0x16c348): undefined reference to `i2c_smbus_read_i2c_block_data'
> > drivers/built-in.o: In function `ak8975_read_raw':
> > >> ak8975.c:(.text+0x16c66b): undefined reference to `i2c_smbus_read_byte_data'
> > >> ak8975.c:(.text+0x16c6a2): undefined reference to `i2c_smbus_read_byte_data'
> > >> ak8975.c:(.text+0x16c6c6): undefined reference to `i2c_smbus_read_byte_data'
> > >> ak8975.c:(.text+0x16c751): undefined reference to `i2c_smbus_read_word_data'
> > drivers/built-in.o: In function `ak8975_driver_init':
> > >> ak8975.c:(.init.text+0x10e35): undefined reference to `i2c_register_driver'
> > drivers/built-in.o: In function `ak8975_driver_exit':
> > >> ak8975.c:(.exit.text+0x1841): undefined reference to `i2c_del_driver'
>
> Yes, something seems to have gone spectacularly wrong here. "rtc:
> ds1685: fix ds1685_rtc_alarm_irq_enable build error" has nothing to do
> with i2c or with drivers/iio/magnetometer/ak8975.c.
>
> And CONFIG_AK8975 depends on CONFIG_I2C.
I've also submitted a patch for this bug:
next prev parent reply other threads:[~2015-02-26 21:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 7:36 kbuild test robot
2015-02-26 20:44 ` Andrew Morton
2015-02-26 21:23 ` Arnd Bergmann [this message]
2015-02-27 15:28 ` Jonathan Cameron
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=2111473.jxZaFqNM44@wuerfel \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=hannes@cmpxchg.org \
--cc=jic23@kernel.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@infradead.org \
/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