From: Randy Dunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: lkml <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
akpm <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] GPIO_SCH and I2C_SCH: select MFD_SUPPORT to eliminate kconfig warnings
Date: Wed, 15 Dec 2010 12:11:09 -0800 [thread overview]
Message-ID: <4D0920DD.3080306@oracle.com> (raw)
In-Reply-To: <20101215101541.5952780f-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
On 12/15/10 01:15, Jean Delvare wrote:
> Hi Randy,
>
> On Tue, 14 Dec 2010 16:26:56 -0800, Randy Dunlap wrote:
>> From: Randy Dunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
>>
>> I2C_ISCH and GPIO_SCH need to select MFD_SUPPORT so that the
>> dependency tree hierarchy is satisfied. This eliminates the
>> kconfig warning:
>>
>> warning: (I2C_ISCH && I2C && PCI || GPIO_SCH && GPIOLIB && PCI) selects LPC_SCH which has unmet direct dependencies (MFD_SUPPORT && PCI)
>>
>> Signed-off-by: Randy Dunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
>> Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>> ---
>> drivers/gpio/Kconfig | 1 +
>> drivers/i2c/busses/Kconfig | 1 +
>> 2 files changed, 2 insertions(+)
>>
>> --- lnx-2637-rc4.orig/drivers/gpio/Kconfig
>> +++ lnx-2637-rc4/drivers/gpio/Kconfig
>> @@ -102,6 +102,7 @@ config GPIO_VR41XX
>> config GPIO_SCH
>> tristate "Intel SCH GPIO"
>> depends on GPIOLIB && PCI
>> + select MFD_SUPPORT
>> select MFD_CORE
>> select LPC_SCH
>> help
>> --- lnx-2637-rc4.orig/drivers/i2c/busses/Kconfig
>> +++ lnx-2637-rc4/drivers/i2c/busses/Kconfig
>> @@ -107,6 +107,7 @@ config I2C_I801
>> config I2C_ISCH
>> tristate "Intel SCH SMBus 1.0"
>> depends on PCI
>> + select MFD_SUPPORT
>> select MFD_CORE
>> select LPC_SCH
>> help
>
> It seems wrong to have to select both MFD_SUPPORT and MFD_CORE. Can't
> the MFD subsystem be cleaned up so that subdrivers have a single symbol
> to select beyond their own?
>
> I don't quite get the point of MFD_CORE. MFD_SUPPORT could be made
> tristate, and MFD_CORE dropped (and then MFD_SUPPORT renamed to
> MFD_CORE to minimize the changes.) This is exactly how I2C support is
> implemented, for example.
OK, I'll look into that. Thanks.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-12-15 20:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 0:26 [PATCH] GPIO_SCH and I2C_SCH: select MFD_SUPPORT to eliminate kconfig warnings Randy Dunlap
[not found] ` <20101214162656.b8550c70.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2010-12-15 9:15 ` Jean Delvare
[not found] ` <20101215101541.5952780f-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2010-12-15 20:11 ` Randy Dunlap [this message]
[not found] ` <4D0920DD.3080306-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2010-12-15 21:21 ` Ben Dooks
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=4D0920DD.3080306@oracle.com \
--to=randy.dunlap-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-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).