[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D2E313D.3040209@oracle.com>
Date: Wed, 12 Jan 2011 14:54:53 -0800
From: Randy Dunlap <randy.dunlap@...cle.com>
To: Len Brown <lenb@...nel.org>
CC: "Rafael J. Wysocki" <rjw@...k.pl>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-acpi@...r.kernel.org,
Stephen Rothwell <sfr@...b.auug.org.au>,
Zhang Rui <rui.zhang@...el.com>, linux-next@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>,
Zimny Lech <napohybelskurwysynom2010@...il.com>
Subject: Re: on builds/randconfigs
On 01/12/11 13:58, Len Brown wrote:
>>> These unusable config combinations should be prevented via Kconfig.
>>> That prevents users from selecting them, which otherwise adds to
>>> our workload and to theirs. It also prevents false-positives
>>> during our useful randconfig testing.
>>
>> But it is kind of difficult to achieve IMhO. For example, there are options
>> that are only SELECTed if something else is set, but randconfig doesn't seem
>> to care.
s/randconfig/kconfig/
> Kconfig select needs to be fixed so that it is not possible to
> select something if that something's dependencies are not met.
>
> This long standing issue is independent of randconfig,
> but Randy can probably attest that a measurable portion
> of the randconfig failures are due to this bug.
Certainly. At least now we have a kconfig warning on this class of
problem.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
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