[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201007162211.31973.arnd@arndb.de>
Date: Fri, 16 Jul 2010 22:11:31 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Nicolas Pitre <nico@...xnic.net>,
"Russell King - ARM Linux" <linux@....linux.org.uk>,
Grant Likely <grant.likely@...retlab.ca>,
Catalin Marinas <catalin.marinas@....com>,
linuxppc-dev@...ts.ozlabs.org,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
linux-kbuild@...r.kernel.org, lkml <linux-kernel@...r.kernel.org>,
linux-arm-kernel@...ts.infradead.org,
Tony Lindgren <tony@...mide.com>,
Daniel Walker <dwalker@...eaurora.org>,
"Uwe Kleine-König"
<u.kleine-koenig@...gutronix.de>,
Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [RFC PATCH] Kconfig: Enable Kconfig fragments to be used for defconfig
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists