From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Michal Marek <mmarek@suse.cz>
Cc: linux-kbuild@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [RFC] add "enable" to the kconfig language
Date: Fri, 14 Sep 2012 10:14:14 +1000 [thread overview]
Message-ID: <20120914101414.1e24b28d2cfa8fc030952a58@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
Hi all,
I have noticed that we use the following paradigm quite a bit theses days:
config <something
select HAVE_<config1>
config <config1>
depends on HAVE_<config1>
or similar
I was wondering if it would make sense to replace this with:
config <something
enable <config1>
config <config1>
depends on enabled
The advantage of this is that we would not have all the HAVE_ config
names in our .config files and the generated include files. Of course,
if config1 does not depend on "enabled", then the "enable <config1>"
would have no effect (we may want to warn about this).
Comments?
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2012-09-14 0:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 0:14 Stephen Rothwell [this message]
2012-09-14 1:49 ` Steven Rostedt
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=20120914101414.1e24b28d2cfa8fc030952a58@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®