From: Len Brown <lenb@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Andrew Morton <akpm@linux-foundation.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
linux-acpi@vger.kernel.org, Zhang Rui <rui.zhang@intel.com>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Zimny Lech <napohybelskurwysynom2010@gmail.com>,
Michal Marek <mmarek@suse.cz>,
Steven Rostedt <rostedt@goodmis.org>,
Linus <torvalds@linux-foundation.org>
Subject: Re: on builds/randconfigs (was: [PATCH -next] thermal: depends on NET)
Date: Wed, 12 Jan 2011 22:31:55 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.02.1101122226340.19754@x980> (raw)
In-Reply-To: <20110113114446.cba7a01f.sfr@canb.auug.org.au>
On Thu, 13 Jan 2011, Stephen Rothwell wrote:
> Hi all,
>
> On Wed, 12 Jan 2011 16:58:26 -0500 (EST) Len Brown <lenb@kernel.org> wrote:
> >
> > Kconfig select needs to be fixed so that it is not possible to
> > select something if that something's dependencies are not met.
>
> So, should the config step fail if such a thing is attempted, or just not
> honour the "select"?
>
> BTW, Linus asked me to investigate the alternative of having "select"
> (recursively) automatically set the dependencies if they are not already
> set ...
I expect that users want to interact only with select.
See feature X, enable feature X, and feature X
selects what is necessary to support what the user requested...
user interact with "depends-on", by comparison, is torture.
Users are not offered options unless the options
already have all of their dependencies met.
If they manually edit the config file and enable such
options, make oldconfig magically throws away their choices.
That drives people crazy.
cheers,
Len Brown, Intel Open Source Technology Center
next prev parent reply other threads:[~2011-01-13 3:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101213163607.0b0a7c3a.sfr@canb.auug.org.au>
[not found] ` <20101213112033.d0060e6c.randy.dunlap@oracle.com>
2011-01-10 17:00 ` [PATCH -next] thermal: depends on NET 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 ` on builds/randconfigs Randy Dunlap
2011-01-13 0:44 ` on builds/randconfigs (was: [PATCH -next] thermal: depends on NET) Stephen Rothwell
2011-01-13 3:31 ` Len Brown [this message]
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
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=alpine.LFD.2.02.1101122226340.19754@x980 \
--to=lenb@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=napohybelskurwysynom2010@gmail.com \
--cc=randy.dunlap@oracle.com \
--cc=rjw@sisk.pl \
--cc=rostedt@goodmis.org \
--cc=rui.zhang@intel.com \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
/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