From: Arnd Bergmann <arnd@arndb.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Nicolas Pitre" <nico@fluxnic.net>,
"Russell King - ARM Linux" <linux@arm.linux.org.uk>,
"Grant Likely" <grant.likely@secretlab.ca>,
"Catalin Marinas" <catalin.marinas@arm.com>,
linuxppc-dev@lists.ozlabs.org,
"Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
linux-kbuild@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org,
"Tony Lindgren" <tony@atomide.com>,
"Daniel Walker" <dwalker@codeaurora.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Stephen Rothwell" <sfr@canb.auug.org.au>
Subject: Re: [RFC PATCH] Kconfig: Enable Kconfig fragments to be used for defconfig
Date: Fri, 16 Jul 2010 22:11:31 +0200 [thread overview]
Message-ID: <201007162211.31973.arnd@arndb.de> (raw)
In-Reply-To: <AANLkTikqHnyFVJF0Pzwy2xtKeNSXYAPFdPkAkLiXK8Ls@mail.gmail.com>
On Friday 16 July 2010 20:46:17 Linus Torvalds wrote:
> Maybe a full "solver" is unnecessary, for example, but just a simple
> "automatically enable the direct dependencies and scream when it's not
> simple any more" would take care of 99% of the common cases, and then
> warn when it needs some manual help.
I think the recursion should also be limited to cases where the
dependency is a valid selectable option, i.e. not for
# this architecture does not support MMIO
config HAS_IOMEM
def_bool 'n'
config PCI
bool "PCI Device drivers"
depends on HAS_IOMEM
config FOO
tristate "Some device driver"
depends on PCI
In this case, it would be straightforward for the solver to enable PCI
for when something selects CONFIG_FOO, but it should print a warning
if this is attempted while HAS_IOMEM is unconditionally disabled,
since that puts it into the "not simple" category.
Arnd
next prev parent reply other threads:[~2010-07-16 20:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 23:04 [RFC PATCH] Kconfig: Enable Kconfig fragments to be used for defconfig Grant Likely
2010-07-13 23:11 ` Grant Likely
2010-07-13 23:14 ` Daniel Walker
2010-07-13 23:21 ` Grant Likely
2010-07-13 23:33 ` Daniel Walker
2010-07-14 0:07 ` Nicolas Pitre
2010-07-14 16:22 ` Daniel Walker
2010-07-16 23:49 ` Jamie Lokier
2010-07-19 5:20 ` Grant Likely
2010-07-16 16:03 ` Catalin Marinas
2010-07-16 17:57 ` Grant Likely
2010-07-16 18:07 ` Russell King - ARM Linux
2010-07-16 18:17 ` Linus Torvalds
2010-07-16 18:18 ` Grant Likely
2010-07-16 18:19 ` Nicolas Pitre
2010-07-16 18:21 ` Grant Likely
2010-07-16 18:31 ` Nicolas Pitre
2010-07-16 18:30 ` Russell King - ARM Linux
2010-07-16 18:40 ` Nicolas Pitre
2010-07-16 18:46 ` Linus Torvalds
2010-07-16 20:09 ` Catalin Marinas
2010-07-16 20:17 ` Grant Likely
2010-07-16 20:29 ` Nicolas Pitre
2010-07-16 20:37 ` Grant Likely
2010-07-16 20:44 ` Catalin Marinas
2010-07-16 20:11 ` Arnd Bergmann [this message]
2010-07-16 18:52 ` Grant Likely
2010-07-16 20:01 ` Arnd Bergmann
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=201007162211.31973.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=catalin.marinas@arm.com \
--cc=dwalker@codeaurora.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nico@fluxnic.net \
--cc=sfr@canb.auug.org.au \
--cc=tony@atomide.com \
--cc=torvalds@linux-foundation.org \
--cc=u.kleine-koenig@pengutronix.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