[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0612181024090.26607@localhost.localdomain>
Date: Mon, 18 Dec 2006 10:31:31 -0500 (EST)
From: "Robert P. J. Day" <rpjday@...dspring.com>
To: Stefan Richter <stefanr@...6.in-berlin.de>
cc: Linux kernel mailing list <linux-kernel@...r.kernel.org>
Subject: Re: [RFC][PATCH] Make entries in the "Device drivers" menu individually
selectable
On Mon, 18 Dec 2006, Stefan Richter wrote:
> Robert P. J. Day wrote:
> [...]
> > in any event, as i mentioned earlier, i'm just trying to find a
> > way to make the menu entries more obvious and more easily
> > selectable, without having to enter each submenu to see what it
> > represents.
> [...]
>
> Yes, this and the points you made in the other post are definitely
> valid.
this is a long-term suggestion, but the easiest solution might be to
introduce a new kbuild directive: "selectablemenu" or something like
that, with a form similar to:
=================
selectablemenu ISDN
bool "ISDN support"
config ...
config ...
config ...
endmenu
=================
the top level entry would be just a yes/no toggle as to whether you
want that support in general, and the internal entries would represent
the submenu and all of them would *automatically* depend on the top
config entry (in this case, ISDN). and the "help" entry could be
available from that top-level entry without having to enter the
submenu. as opposed to what you need to do now.
i'm guessing that structure would be sufficient for 90% of the
current menu layouts. just a thought.
rday
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists