From: Samuel Ortiz <sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: Cory Maccarrone
<darkstar6262-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v3] [MFD] i2c-htcpld: Add the HTCPLD driver
Date: Tue, 19 Jan 2010 13:09:48 +0100 [thread overview]
Message-ID: <20100119120947.GD554@sortiz.org> (raw)
In-Reply-To: <20100119124812.345fe447-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
Hi Jean,
On Tue, Jan 19, 2010 at 12:48:12PM +0100, Jean Delvare wrote:
> Hi Samuel,
>
> On Tue, 19 Jan 2010 12:09:17 +0100, Samuel Ortiz wrote:
> > 2) Kconfig: we need to depend on I2C=y, to avoid the problematic case of
> > having I2C_CORE=m and HTC_I2CPLD=y
>
> ??
>
> There is no config option named I2C_CORE. The main option for I2C is,
> well, I2C,
Sorry, I meant I2C, not I2C_CORE.
> and if you depend on I2C, then you can't be built into the
> kernel if I2C is built as a module.
I have:
drivers/mfd/Kconfig:
config HTC_I2CPLD
bool "HTC I2C PLD chip support"
depends on I2C
Then make menuconfig allows me to build a .config with
CONFIG_I2C=m and CONFIG_HTC_I2CPLD=y
and that obviously fails to build. If I'm a bool depending on I2C, it has to
be a built-in I2C.
Cheers,
Samuel.
> What exact problem are you trying to solve?
>
> --
> Jean Delvare
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2010-01-19 12:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 1:38 [PATCH v3] [MFD] i2c-htcpld: Add the HTCPLD driver Cory Maccarrone
[not found] ` <1260841135-6680-1-git-send-email-darkstar6262-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-01-06 12:35 ` Samuel Ortiz
[not found] ` <20100106123532.GB5500-jcdQHdrhKHMdnm+yROfE0A@public.gmane.org>
2010-01-06 14:47 ` Cory Maccarrone
[not found] ` <6cb013311001060647s3bce5e63mbae1a10036a14ae1-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-09 16:55 ` Cory Maccarrone
[not found] ` <1263056154-20085-1-git-send-email-darkstar6262-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-01-18 12:48 ` Samuel Ortiz
[not found] ` <20100118124855.GB8036-jcdQHdrhKHMdnm+yROfE0A@public.gmane.org>
2010-01-18 15:36 ` Samuel Ortiz
[not found] ` <20100118153624.GA13811-jcdQHdrhKHMdnm+yROfE0A@public.gmane.org>
2010-01-18 21:23 ` Cory Maccarrone
[not found] ` <6cb013311001181323q79aba15dif165ff41d79734a7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-19 11:09 ` Samuel Ortiz
[not found] ` <20100119110916.GB554-jcdQHdrhKHMdnm+yROfE0A@public.gmane.org>
2010-01-19 11:48 ` Jean Delvare
[not found] ` <20100119124812.345fe447-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2010-01-19 12:09 ` Samuel Ortiz [this message]
[not found] ` <20100119120947.GD554-jcdQHdrhKHMdnm+yROfE0A@public.gmane.org>
2010-01-19 12:14 ` Jean Delvare
[not found] ` <20100119131402.7e465fdb-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2010-01-19 15:10 ` Cory Maccarrone
[not found] ` <6cb013311001190710q186405c7m1193af79e18a09e3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-03-07 18:03 ` Cory Maccarrone
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=20100119120947.GD554@sortiz.org \
--to=sameo-vuqaysv1563yd54fqh9/ca@public.gmane.org \
--cc=darkstar6262-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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).