From: Randy Dunlap <rdunlap@infradead.org>
To: Jim Davis <jim.epost@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next <linux-next@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
wsa@the-dreams.de, khali@linux-fr.org,
Paul Gortmaker <paul.gortmaker@windriver.com>,
linux-i2c@vger.kernel.org,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
linux-can@vger.kernel.org,
linux-media <linux-media@vger.kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: randconfig build error with next-20141001, in drivers/i2c/algos/i2c-algo-bit.c
Date: Wed, 01 Oct 2014 16:26:11 -0700 [thread overview]
Message-ID: <542C8D93.8090008@infradead.org> (raw)
In-Reply-To: <CA+r1ZhiL1y9aeLeJjpd_1DtzOG_oyoPg7XsTPJ9G-XY5G2DfCQ@mail.gmail.com>
On 10/01/14 14:37, Jim Davis wrote:
> Building with the attached random configuration file,
Also:
warning: (CAN_PEAK_PCIEC && SFC && IGB && VIDEO_TW68 && DRM && FB_DDC && FB_VIA) selects I2C_ALGOBIT which has unmet direct dependencies (I2C)
> drivers/i2c/algos/i2c-algo-bit.c: In function ‘i2c_bit_add_bus’:
> drivers/i2c/algos/i2c-algo-bit.c:658:33: error: ‘i2c_add_adapter’
> undeclared (first use in this function)
> return __i2c_bit_add_bus(adap, i2c_add_adapter);
> ^
> drivers/i2c/algos/i2c-algo-bit.c:658:33: note: each undeclared
> identifier is reported only once for each function it appears in
> drivers/i2c/algos/i2c-algo-bit.c: In function ‘i2c_bit_add_numbered_bus’:
> drivers/i2c/algos/i2c-algo-bit.c:664:33: error:
> ‘i2c_add_numbered_adapter’ undeclared (first use in this function)
> return __i2c_bit_add_bus(adap, i2c_add_numbered_adapter);
> ^
> CC net/openvswitch/actions.o
> drivers/i2c/algos/i2c-algo-bit.c: In function ‘i2c_bit_add_bus’:
> drivers/i2c/algos/i2c-algo-bit.c:659:1: warning: control reaches end of non-void
> function [-Wreturn-type]
> }
> ^
> drivers/i2c/algos/i2c-algo-bit.c: In function ‘i2c_bit_add_numbered_bus’:
> drivers/i2c/algos/i2c-algo-bit.c:665:1: warning: control reaches end of non-void
> function [-Wreturn-type]
> }
> ^
> make[3]: *** [drivers/i2c/algos/i2c-algo-bit.o] Error 1
In drivers/media/pci/tw68/Kconfig, VIDEO_TW68 should depend on I2C in order
to make it safe to select I2C_ALGOBIT.
In drivers/net/can/sja1000/Kconfig, CAN_PEAK_PCIEC should depend on I2C
instead of selecting I2C (and change the help text).
--
~Randy
next prev parent reply other threads:[~2014-10-01 23:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 21:37 randconfig build error with next-20141001, in drivers/i2c/algos/i2c-algo-bit.c Jim Davis
2014-10-01 23:26 ` Randy Dunlap [this message]
2014-10-06 8:06 ` Oliver Hartkopp
2014-10-06 16:52 ` Randy Dunlap
2014-10-06 17:39 ` Oliver Hartkopp
2014-10-06 18:09 ` Randy Dunlap
2014-10-07 8:58 ` Oliver Hartkopp
2014-10-07 12:37 ` Stephane Grosjean
[not found] ` <5433AB31.9090603-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
2014-10-07 17:03 ` Randy Dunlap
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=542C8D93.8090008@infradead.org \
--to=rdunlap@infradead.org \
--cc=hverkuil@xs4all.nl \
--cc=jim.epost@gmail.com \
--cc=khali@linux-fr.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=sfr@canb.auug.org.au \
--cc=wsa@the-dreams.de \
/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).