linux-kernel - Re: [RFC] USB Kconfig: Declutter USB Kconfig Menu

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20071222072208.A0960230DE8@adsl-69-226-248-13.dsl.pltn13.pacbell.net>
Date:	Fri, 21 Dec 2007 23:22:08 -0800
From:	David Brownell <david-b@...bell.net>
To:	jengelh@...putergmbh.de, a1426z@...ab.com
Cc:	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
	greg@...ah.com
Subject: Re: [RFC] USB Kconfig: Declutter USB Kconfig Menu

> > 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.

- Dave

--
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/