From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Anton Vorontsov <cbou@mail.ru>,
Rodolfo Giometti <giometti@linux.it>
Subject: Re: linux-next: Tree for May 7 (bq27x00_battery)
Date: Tue, 07 May 2013 10:21:21 -0700 [thread overview]
Message-ID: <51893811.8080102@infradead.org> (raw)
In-Reply-To: <20130507134922.981483ab1e5cb09e5543a6cc@canb.auug.org.au>
On 05/06/13 20:49, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any v3.11 destined work to your linux-next included
> branches until after v3.10-rc1 is released.
>
> I am receiving a (un)reasonable number of conflicts from there being
> multiple copies of some commits in various trees. Please clean this up
> and resist the temptataion to rebase your trees on the way to your
> upstream ...
>
> Changes since 20130506:
>
on x86_64:
drivers/built-in.o: In function `bq27x00_read_i2c':
bq27x00_battery.c:(.text+0x169e20): undefined reference to `i2c_transfer'
bq27x00_battery.c:(.text+0x169e44): undefined reference to `i2c_transfer'
drivers/built-in.o: In function `bq27x00_battery_init':
bq27x00_battery.c:(.init.text+0x82af): undefined reference to `i2c_register_driver'
drivers/built-in.o: In function `bq27x00_battery_exit':
bq27x00_battery.c:(.exit.text+0xd8f): undefined reference to `i2c_del_driver'
when CONFIG_I2C=m and CONFIG_BATTERY_BQ27X00_I2C=y.
--
~Randy
next prev parent reply other threads:[~2013-05-07 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 3:49 linux-next: Tree for May 7 Stephen Rothwell
2013-05-07 17:01 ` linux-next: Tree for May 7 (usb/chipidea) Randy Dunlap
2013-05-07 17:08 ` linux-next: Tree for May 7 (iio) Randy Dunlap
[not found] ` <51893523.9000105-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2013-05-07 18:12 ` Lars-Peter Clausen
2013-05-07 17:21 ` Randy Dunlap [this message]
2013-05-10 18:46 ` linux-next: Tree for May 7 (bq27x00_battery) Anton Vorontsov
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=51893811.8080102@infradead.org \
--to=rdunlap@infradead.org \
--cc=cbou@mail.ru \
--cc=giometti@linux.it \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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).