From: Lee Jones <lee.jones@linaro.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Florian Lobmaier <florian.lobmaier@ams.com>,
Laxman Dewangan <ldewangan@nvidia.com>
Subject: Re: linux-next: Tree for Nov 19 (mfd/as3722)
Date: Tue, 19 Nov 2013 19:38:09 +0000 [thread overview]
Message-ID: <20131119193809.GD19953@lee--X1> (raw)
In-Reply-To: <528B9F03.6040601@infradead.org>
On Tue, 19 Nov 2013, Randy Dunlap wrote:
> On 11/18/13 19:39, Stephen Rothwell wrote:
> > Hi all,
> >
> > Please do *not* add any v3.14 material to linux-next until after
> > v3.13-rc1 is released.
> >
> > Changes since 20131118:
> >
>
> on i386:
>
> when CONFIG_I2C=m
> (a.k.a. the dangers of having a bool depend on a tristate)
>
> drivers/built-in.o: In function `as3722_i2c_probe':
> as3722.c:(.text+0x41456): undefined reference to `devm_regmap_init_i2c'
> drivers/built-in.o: In function `as3722_i2c_driver_init':
> as3722.c:(.init.text+0x1b5d): undefined reference to `i2c_register_driver'
> drivers/built-in.o: In function `as3722_i2c_driver_exit':
> as3722.c:(.exit.text+0x41e): undefined reference to `i2c_del_driver'
I accepted a patch which fixes this yesterday and intended to send post -rc1.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2013-11-19 19:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 3:39 linux-next: Tree for Nov 19 Stephen Rothwell
2013-11-19 4:08 ` Guenter Roeck
2013-11-19 4:47 ` Stephen Rothwell
2013-11-19 17:25 ` linux-next: Tree for Nov 19 (mfd/as3722) Randy Dunlap
2013-11-19 19:38 ` Lee Jones [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=20131119193809.GD19953@lee--X1 \
--to=lee.jones@linaro.org \
--cc=florian.lobmaier@ams.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.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).