From: Randy Dunlap <randy.dunlap@Oracle.com>
To: Len Brown <lenb@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Andrew Morton <akpm@linux-foundation.org>,
linux-acpi@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Zhang Rui <rui.zhang@intel.com>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Zimny Lech <napohybelskurwysynom2010@gmail.com>
Subject: Re: on builds/randconfigs
Date: Wed, 12 Jan 2011 14:54:53 -0800 [thread overview]
Message-ID: <4D2E313D.3040209@oracle.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1101121654000.19754@x980>
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 ***
next prev parent reply other threads:[~2011-01-12 22:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 5:36 linux-next: Tree for December 13 Stephen Rothwell
2010-12-13 19:20 ` [PATCH -next] thermal: depends on NET Randy Dunlap
2010-12-20 16:47 ` Randy Dunlap
2011-01-04 17:10 ` Randy Dunlap
2011-01-10 17:00 ` Randy Dunlap
2011-01-12 5:18 ` Len Brown
2011-01-12 17:48 ` on builds/randconfigs (was: [PATCH -next] thermal: depends on NET) Randy Dunlap
2011-01-12 18:35 ` Len Brown
2011-01-12 18:38 ` on builds/randconfigs Randy Dunlap
2011-01-12 21:52 ` Len Brown
2011-01-12 21:18 ` on builds/randconfigs (was: [PATCH -next] thermal: depends on NET) Andrew Morton
2011-01-12 21:24 ` Rafael J. Wysocki
2011-01-12 21:58 ` Len Brown
2011-01-12 22:15 ` Valdis.Kletnieks
2011-01-12 22:54 ` Randy Dunlap [this message]
2011-01-13 0:44 ` Stephen Rothwell
2011-01-13 3:31 ` Len Brown
2011-01-13 3:45 ` Steven Rostedt
2011-01-13 3:48 ` Stephen Rothwell
2011-01-13 4:08 ` Linus Torvalds
2011-01-13 12:23 ` on builds/randconfigs Michal Marek
2011-01-15 12:24 ` Vegard Nossum
2011-01-15 16:09 ` Michal Marek
2010-12-13 19:44 ` [PATCH -next] cs5535: fix printk format warnings Randy Dunlap
2010-12-13 20:28 ` [PATCH V2 " Joe Perches
2010-12-13 20:42 ` Randy Dunlap
2010-12-13 20:57 ` [PATCH V3 " Joe Perches
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=4D2E313D.3040209@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=napohybelskurwysynom2010@gmail.com \
--cc=rjw@sisk.pl \
--cc=rui.zhang@intel.com \
--cc=sfr@canb.auug.org.au \
/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.