From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] Make entries in the "Device drivers" menu individually selectable
Date: Mon, 18 Dec 2006 04:38:39 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0612180431160.16929@localhost.localdomain> (raw)
In-Reply-To: <4583D008.40806@s5r6.in-berlin.de>
On Sat, 16 Dec 2006, Stefan Richter wrote:
> Robert P. J. Day wrote on 2006-12-14:
> > i've posted on this before so here's a slightly-updated patch
> > that uses the kbuild "menuconfig" feature to make numerous entries
> > under the Device drivers menu selectable on the spot.
>
> Works for me, but I don't see a lot of benefit from it. Actually I
> see two disadvantages of the patch:
>
> - Without the patch, the choice of y/m/n for a subsystem and the
> help text is put aside into the submenu. I find this current layout
> simpler and quieter.
it's certainly "simpler and quieter" in one sense, but one need only
look at a submenu like "Network device support" to see a very "loud"
menu, so it's not like this patch would be introducing an
unprecedented level of noise.
also, in the Device Drivers menu, i find it slightly annoying that i
have to *enter* a submenu to read its help information. if i see the
entry, say, "Dallas's 1-wire bus" and i have no idea what that is and
select "Help", i get the generic help screen. i need to select that
entry and enter the submenu just to read its top-level help.
in any event, i'm sure folks understand what i'm after here. if
there's a cleaner and more efficient way to do this, that would work
for me.
rday
next prev parent reply other threads:[~2006-12-18 9:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 8:31 Robert P. J. Day
2006-12-16 10:52 ` Stefan Richter
2006-12-16 17:58 ` Jan Engelhardt
2006-12-18 9:38 ` Robert P. J. Day [this message]
2006-12-18 9:50 ` Robert P. J. Day
2006-12-18 15:02 ` Stefan Richter
2006-12-18 15:31 ` Robert P. J. Day
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=Pine.LNX.4.64.0612180431160.16929@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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®