From: Tomas Szepe <szepe@pinerecords.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: "Robert P. J. Day" <rpjday@mindspring.com>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: observations on 2.5 config screens
Date: Thu, 2 Jan 2003 03:54:01 +0100 [thread overview]
Message-ID: <20030102025401.GI17053@louise.pinerecords.com> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0301011750010.21149-100000@dragon.pdx.osdl.net>
> [rddunlap@osdl.org]
>
> On Wed, 1 Jan 2003, Tomas Szepe wrote:
>
> [snippage]
> | > It seems that the final option, "Preemptible kernel", does
> | > not belong there. In fact, there seem to be a number of
> | > kernel-related, kind of hacking/debugging options, that
> | > could be collected in one place, like preemption, sysctl,
> | > hacking, executable file formats, etc. "Low-level kernel
> | > options", perhaps?
>
> So long as they come after the processor selection or whatever
> dependencies they have.
No longer an issue, see below.
> ...
>
> | > Multimedia devices
> | >
> | > How come "Sound" is not here? And (as we've already
> | > established), Radio Adapters is not a sub-entry of Video for
> | > Linux. :-) (And is there a reason why Amateur Radio Support
> | > and Radio Adapters are so far apart in the config menus?
>
> I agree.
>
> Greg Banks has (had) a real nice program for checking
> dependency ordering using Config.in files. It would be
> very nice if it now worked with Kconfig files. :)
Forward references work nicely with the new configurator,
see for yourself (patch against 2.5.53):
diff -urN a/init/Kconfig b/init/Kconfig
--- a/init/Kconfig 2002-12-16 07:02:05.000000000 +0100
+++ b/init/Kconfig 2003-01-02 03:49:02.000000000 +0100
@@ -1,6 +1,10 @@
menu "Code maturity level options"
+config HRM0PS
+ depends on HRMOPS_PREREQUISITE
+ bool "This proves that forward-referenced symbols work just fine"
+
config EXPERIMENTAL
bool "Prompt for development and/or incomplete code/drivers"
---help---
diff -urN a/net/Kconfig b/net/Kconfig
--- a/net/Kconfig 2002-12-08 20:06:41.000000000 +0100
+++ b/net/Kconfig 2003-01-02 03:49:44.000000000 +0100
@@ -5,6 +5,9 @@
menu "Networking options"
depends on NET
+config HRMOPS_PREREQUISITE
+ bool "Switch this on for some serious HRM0PS!!"
+
config PACKET
tristate "Packet socket"
---help---
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2003-01-02 2:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-01 19:55 observations on 2.5 config screens Robert P. J. Day
2003-01-01 20:07 ` Tomas Szepe
2003-01-01 20:15 ` Robert P. J. Day
2003-01-01 20:26 ` John Bradford
2003-01-02 1:55 ` Randy.Dunlap
2003-01-02 2:32 ` Robert P. J. Day
2003-01-02 4:10 ` Randy.Dunlap
2003-01-02 2:54 ` Tomas Szepe [this message]
2003-01-07 23:07 ` [2.5 patch] MODULE_FORCE_UNLOAD must depend on MODULE_UNLOAD Adrian Bunk
2003-01-08 12:05 ` Rusty Russell
2003-01-07 23:30 ` observations on 2.5 config screens Adrian Bunk
2003-01-07 23:42 ` Robert Love
2003-01-08 0:14 ` Russell King
2003-01-08 14:32 ` Bill Davidsen
2003-01-08 15:53 ` Robert Love
2003-01-08 18:36 ` Bill Davidsen
2003-01-08 19:50 ` Dave Jones
2003-01-08 22:49 ` Bill Davidsen
2003-01-09 12:50 ` Dave Jones
2003-01-09 16:12 ` Bill Davidsen
2003-01-09 13:38 ` Ruslan U. Zakirov
[not found] <Pine.LNX.4.44.0301011435300.27623-100000@dell.qualified-at.bofh.it>
2003-01-02 23:50 ` Bill Davidsen
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=20030102025401.GI17053@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=rpjday@mindspring.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