From: Al Boldi <a1426z@gawab.com>
To: David Brownell <david-b@pacbell.net>, jengelh@computergmbh.de
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: [RFC] USB Kconfig: Declutter USB Kconfig Menu
Date: Sat, 22 Dec 2007 16:49:55 +0300 [thread overview]
Message-ID: <200712221649.55831.a1426z@gawab.com> (raw)
In-Reply-To: <20071222072208.A0960230DE8@adsl-69-226-248-13.dsl.pltn13.pacbell.net>
David Brownell wrote:
> > > Which is why my suggestion was to have them both move up a level, with
> > > host and peripheral side menus nested normally:
> > >
> > > Device Drivers:
> > > ...
> > > [ ] HID devices
> > > < > Host side USB
> > > < > Peripheral side USB
> > > < > MMC/SD/SDIO card support
> > > [ ] LED support
> > > ...
> > >
> > > That way both host and peripheral side support would have their own
> > > menu, and that pointless nesting would be reduced.
> >
> > You mean:
> > [ ] Host side USB
> > [ ] Peripheral side USB
> >
> > Right?
>
> Both of those subsystems are already set up with the main choice
> as tristate "< >/<M>/<*>". If we're simplifying the navigation,
> I can't see a point to requiring *two* menu actions not one.
There is a point, but it's a weak one: you want it to unfold in the same menu
as you select the option. So, if you unfold the sub-options in a separate
sub-menu, you better use [ ] (or just blank), as this will allow you to
enter the sub-menu, and see the unfold take place inside the same menu.
IMHO, I prefer < >, but newbies probably prefer [ ], as it is less abstract.
Provided there is agreement, and we go with < >, it would mean a slight
change to Host side USB, like this (note new USB Core Config sub-menu):
--- Support for Host-side USB
[ ] USB Core Config --->
[ ] USB Host Controller Drivers --->
--- NOTE: USB_STORAGE needs SCSI, and 'SCSI disk support' may
--- also be needed; see USB_STORAGE Help for more information
< > USB Mass Storage support --->
[ ] The shared table of common (or usual) storage devices
[ ] USB Monitor
< > USS720 parport driver
< > USB Serial Converter support --->
< > USB DSL modem support --->
[ ] USB Device Class drivers --->
[ ] USB Imaging devices --->
[ ] USB Miscellaneous drivers --->
Thanks!
--
Al
next prev parent reply other threads:[~2007-12-22 13:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-21 13:30 Al Boldi
2007-12-21 21:16 ` Jan Engelhardt
2007-12-21 23:58 ` David Brownell
[not found] ` <200712220806.24730.a1426z@gawab.com>
2007-12-22 6:19 ` David Brownell
2007-12-22 6:51 ` Al Boldi
2007-12-22 7:22 ` David Brownell
2007-12-22 13:49 ` Al Boldi [this message]
2007-12-23 6:07 ` David Brownell
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=200712221649.55831.a1426z@gawab.com \
--to=a1426z@gawab.com \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.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®