From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: balbi@ti.com
Cc: Sam Ravnborg <sam@ravnborg.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-kbuild@vger.kernel.org
Subject: Re: Kconfig "softdepends" idea
Date: Tue, 30 Apr 2013 14:10:03 +0300 [thread overview]
Message-ID: <517FA68B.20001@ti.com> (raw)
In-Reply-To: <20130430103318.GB12161@arwen.pp.htv.fi>
[-- Attachment #1: Type: text/plain, Size: 2150 bytes --]
On 04/30/2013 01:33 PM, Felipe Balbi wrote:
> Hi,
>
> On Tue, Apr 30, 2013 at 12:24:40PM +0200, Sam Ravnborg wrote:
>>> So, my idea is to have a new kind of Kconfig dependency. I'll call it
>>> "softdepends" in lack of better name. A driver maintainer could use
>>> "softdepends on ARCH_OMAP", instead of "depends on ARCH_OMAP", to say
>>> that this driver does not actually build depend on ARCH_OMAP, but for
>>> all normal purposes it does.
>>>
>>> Normally, this would result in the same behavior as the normal
>>> "depends", and Linus would not get a questions whether he wants to
>>> enable this OMAP specific driver or not, and the driver would not be
>>> visible on the menuconfig.
>>>
>>> But the user could enable the driver if he explicitly so wants. Perhaps
>>> a Kconfig option such as "ignore softdepends", enabling of which would
>>> allow the user to enable the drivers that use softdepends. Or, maybe
>>> just require the user to add the config option manually into his .config.
>>
>> If I understand you correct this is already possible today without
>> extending the kconfig language.
>>
>> config OMAP_SPECIFIC_DRIVER
>> depends on ARCH_OMAP || SHOW_ALL_DRIVERS
>>
>>
>> If SHOW_ALL_DRIVERS are "y" then user can say "y" to the OMAP specific
>> driver too, even without ARCH_OMAP being selected.
>
> SHOW_ALL_DRIVERS might create another set of issues. If Linus isn't
> taking patches removing 'depends on ARCH_OMAP' would he take patches
> adding SHOW_ALL_DRIVERS ?
Wouldn't the SHOW_ALL_DRIVERS be just a one time query from Kconfig to
the user? So Linus only needs to say "n" once. Why would he object to that?
Then again, as a personal opinion, "depends on ARCH_OMAP ||
SHOW_ALL_DRIVERS" is not very descriptive. I'm not sure if that matters,
though. One doesn't need to read the Kconfig files every day =).
But presuming most of the drivers would use that, it would add quite a
bit of repetition to the Kconfig files. Well, ok, I have no idea how
many drivers have dependencies that could be removed.
So SHOW_ALL_DRIVERS sounds quite an easy solution to this.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: <balbi@ti.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
<linux-kbuild@vger.kernel.org>
Subject: Re: Kconfig "softdepends" idea
Date: Tue, 30 Apr 2013 14:10:03 +0300 [thread overview]
Message-ID: <517FA68B.20001@ti.com> (raw)
In-Reply-To: <20130430103318.GB12161@arwen.pp.htv.fi>
[-- Attachment #1: Type: text/plain, Size: 2150 bytes --]
On 04/30/2013 01:33 PM, Felipe Balbi wrote:
> Hi,
>
> On Tue, Apr 30, 2013 at 12:24:40PM +0200, Sam Ravnborg wrote:
>>> So, my idea is to have a new kind of Kconfig dependency. I'll call it
>>> "softdepends" in lack of better name. A driver maintainer could use
>>> "softdepends on ARCH_OMAP", instead of "depends on ARCH_OMAP", to say
>>> that this driver does not actually build depend on ARCH_OMAP, but for
>>> all normal purposes it does.
>>>
>>> Normally, this would result in the same behavior as the normal
>>> "depends", and Linus would not get a questions whether he wants to
>>> enable this OMAP specific driver or not, and the driver would not be
>>> visible on the menuconfig.
>>>
>>> But the user could enable the driver if he explicitly so wants. Perhaps
>>> a Kconfig option such as "ignore softdepends", enabling of which would
>>> allow the user to enable the drivers that use softdepends. Or, maybe
>>> just require the user to add the config option manually into his .config.
>>
>> If I understand you correct this is already possible today without
>> extending the kconfig language.
>>
>> config OMAP_SPECIFIC_DRIVER
>> depends on ARCH_OMAP || SHOW_ALL_DRIVERS
>>
>>
>> If SHOW_ALL_DRIVERS are "y" then user can say "y" to the OMAP specific
>> driver too, even without ARCH_OMAP being selected.
>
> SHOW_ALL_DRIVERS might create another set of issues. If Linus isn't
> taking patches removing 'depends on ARCH_OMAP' would he take patches
> adding SHOW_ALL_DRIVERS ?
Wouldn't the SHOW_ALL_DRIVERS be just a one time query from Kconfig to
the user? So Linus only needs to say "n" once. Why would he object to that?
Then again, as a personal opinion, "depends on ARCH_OMAP ||
SHOW_ALL_DRIVERS" is not very descriptive. I'm not sure if that matters,
though. One doesn't need to read the Kconfig files every day =).
But presuming most of the drivers would use that, it would add quite a
bit of repetition to the Kconfig files. Well, ok, I have no idea how
many drivers have dependencies that could be removed.
So SHOW_ALL_DRIVERS sounds quite an easy solution to this.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2013-04-30 11:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 9:52 Kconfig "softdepends" idea Tomi Valkeinen
2013-04-30 9:52 ` Tomi Valkeinen
2013-04-30 10:24 ` Sam Ravnborg
2013-04-30 10:33 ` Felipe Balbi
2013-04-30 10:33 ` Felipe Balbi
2013-04-30 11:10 ` Tomi Valkeinen [this message]
2013-04-30 11:10 ` Tomi Valkeinen
2013-04-30 11:40 ` Sam Ravnborg
2013-04-30 12:01 ` Tomi Valkeinen
2013-04-30 12:01 ` Tomi Valkeinen
2013-04-30 11:36 ` Sam Ravnborg
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=517FA68B.20001@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=balbi@ti.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.