From: Roland Dreier <rdreier@cisco.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: [build bug] undefined reference to `i2c_attach_client'
Date: Fri, 01 Feb 2008 13:26:18 -0800 [thread overview]
Message-ID: <aday7a4jrlx.fsf@cisco.com> (raw)
In-Reply-To: <20080201135836.GA20294@elte.hu> (Ingo Molnar's message of "Fri, 1 Feb 2008 14:58:36 +0100")
> > randconfig testing found the following build bug in latest -git:
> >
> > drivers/built-in.o: In function `v4l2_i2c_attach':
> > : undefined reference to `i2c_attach_client'
I hit this too -- it seems that commit 8ffbc655 ("V4L/DVB (6451):
v4l2: add support for bus-based I2C drivers"), which added
v4l2_i2c_attach() without adding any dependency on CONFIG_I2C. Not
sure what the correct fix is -- either CONFIG_VIDEO_DEV needs to
select/depend on CONFIG_I2C, or v4l2_i2c_attach() should only be built
if CONFIG_I2C is on.
prev parent reply other threads:[~2008-02-01 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 12:09 [build bug] undefined reference to `i2c_attach_client' Ingo Molnar
2008-02-01 13:58 ` Ingo Molnar
2008-02-01 21:26 ` Roland Dreier [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=aday7a4jrlx.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mingo@elte.hu \
/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