From: Tomas Szepe <szepe@pinerecords.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: [RFC] top-level config menu dependencies
Date: Wed, 1 Jan 2003 17:25:19 +0100 [thread overview]
Message-ID: <20030101162519.GF15200@louise.pinerecords.com> (raw)
Hi,
It has been a long-time tradition that no "real tunable options" are
present in the top level of the kernel config menu. I reckon this has
to do with an inherent limitation of the original config subsystem.
While converting the way submenus appear in menuconfig depending on
their main, parent config option, I stumbled upon certain subsystems
(such as MTD or IrDA) that should clearly have an on/off switch directly
in the main menu so that one doesn't have to enter the corresponding
submenus to even see if they're enabled or disabled.
Since the new kernel configurator would have no problems with such
a setup, I'm posting this RFC to get the general opinion on whether
this should be carried on with. I'm willing to create and send in
the patches.
Regards,
--
Tomas Szepe <szepe@pinerecords.com>
next reply other threads:[~2003-01-01 16:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-01 16:25 Tomas Szepe [this message]
2003-01-01 16:32 ` [RFC] top-level config menu dependencies John Bradford
2003-01-01 16:42 ` Tomas Szepe
2003-01-02 13:32 ` Roman Zippel
2003-01-02 19:50 ` Tomas Szepe
2003-01-03 1:45 ` Roman Zippel
2003-01-03 23:46 ` [PATCH] menuconfig support for " Roman Zippel
2003-01-04 4:27 ` Tomas Szepe
2003-01-04 4:53 ` Tomas Szepe
2003-01-04 15:52 ` Menuconfig " Tomas Szepe
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=20030101162519.GF15200@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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