From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
zippel@linux-m68k.org, jejb <james.bottomley@steeleye.com>
Subject: Re: how to handle indirect kconfig dependencies
Date: Fri, 17 Nov 2006 14:55:09 +0100 [thread overview]
Message-ID: <455DBF3D.40801@s5r6.in-berlin.de> (raw)
In-Reply-To: <20061116200741.fb607fe4.randy.dunlap@oracle.com>
Randy Dunlap wrote:
> I have a (randconfig) build of 2.6.19-rc5-mm2 with:
[...]
> so the question is:
> (How) can kconfig follow the dependency chain and either
> - prevent this odd config combination or
> - see that 'select DEBUG_FS' implies 'select SYSFS' and then enable SYSFS
> ?
>
> I don't believe that the right answer is to add
> depends on SYSFS
> to DEBUG_READAHEAD.
I know this doesn't concludingly answer your question, but: All of the
various shipped tools to generate .config need to be fixed to recognize
"select" to imply a dependency like "depends on" does.
[...]
> ~Randy [or just kill off select]
Or this. ("select" appears to be useful for dialog driven creation of
.config in cases where developers are able to predetermine preferences
of users --- nothing more and nothing less.)
--
Stefan Richter
-=====-=-==- =-== =---=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2006-11-17 13:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 4:07 how to handle indirect kconfig dependencies Randy Dunlap
2006-11-17 13:55 ` Stefan Richter [this message]
2006-11-20 18:13 ` Adrian Bunk
2006-11-20 18:56 ` Stefan Richter
2006-11-20 22:09 ` James Bottomley
2006-11-26 3:46 ` Randy Dunlap
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=455DBF3D.40801@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=james.bottomley@steeleye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=zippel@linux-m68k.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