[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.0908211309020.30182@gandalf.stny.rr.com>
Date: Fri, 21 Aug 2009 13:39:02 -0400 (EDT)
From: Steven Rostedt <rostedt@...dmis.org>
To: Ingo Molnar <mingo@...e.hu>
cc: Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, tglx@...utronix.de,
peterz@...radead.org, torvalds@...ux-foundation.org, tytso@....edu,
arjan@...radead.org, greg@...ah.com, mcgrof@...il.com,
zippel@...ux-m68k.org, linux-kbuild@...r.kernel.org,
sam@...nborg.org, corbet@....net, sourcejedi.lkml@...glemail.com,
andi@...stfloor.org, Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org
Subject: Re: [PATCH 00/14] kconfig: streamline distro configs for testers
On Fri, 21 Aug 2009, Ingo Molnar wrote:
> * Steven Rostedt <rostedt@...dmis.org> wrote:
>
> I'm wondering, what do you think about Vegard's 'warn about complex
> selects' feature for kconfig which he submitted some time ago:
>
> http://lkml.org/lkml/2008/5/4/13
>
> That's a really sore kconfig spot we have. It's not a bug, but it
> sure bites people again and again, and it would be nice to have some
> built-in mechanism that gently nudges us away from complex selects.
> (many of which are inadvertent or become complex after the fact)
I'll take a look at that too. We need to be careful about kicking out too
many warnings. Perhaps a "make configcheck" is in order that will do
various checks. This is very similar to my check for select dependency
error patch:
http://lkml.org/lkml/2009/2/21/2
I may take a look at getting both of these in (or a merge of the two).
-- Steve
--
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