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,
Jonathan Cameron <jic23@cam.ac.uk>,
linux-iio@vger.kernel.org
Subject: Re: linux-next: Tree for May 7 (iio)
Date: Tue, 07 May 2013 10:08:51 -0700 [thread overview]
Message-ID: <51893523.9000105@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:
when CONFIG_AD5446=y and CONFIG_I2C=m:
drivers/built-in.o: In function `ad5622_write':
ad5446.c:(.text+0xae0b5): undefined reference to `i2c_master_send'
drivers/built-in.o: In function `ad5446_init':
ad5446.c:(.init.text+0x4f28): undefined reference to `i2c_register_driver'
drivers/built-in.o: In function `ad5446_i2c_unregister_driver':
ad5446.c:(.exit.text+0xc73): undefined reference to `i2c_del_driver'
--
~Randy
next prev parent reply other threads:[~2013-05-07 17:09 UTC|newest]
Thread overview: 8+ 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 3:49 ` Stephen Rothwell
2013-05-07 17:01 ` linux-next: Tree for May 7 (usb/chipidea) Randy Dunlap
2013-05-07 17:08 ` Randy Dunlap [this message]
2013-05-07 18:12 ` linux-next: Tree for May 7 (iio) Lars-Peter Clausen
2013-05-07 18:12 ` Lars-Peter Clausen
2013-05-07 17:21 ` linux-next: Tree for May 7 (bq27x00_battery) Randy Dunlap
2013-05-10 18:46 ` 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=51893523.9000105@infradead.org \
--to=rdunlap@infradead.org \
--cc=jic23@cam.ac.uk \
--cc=linux-iio@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.