Messages in this thread | | | Date | Sat, 26 Mar 2005 17:10:02 -0800 | From | "Randy.Dunlap" <> | Subject | Re: [ARM] Group device drivers together under their own menu |
| |
Matthew Wilcox wrote: > On Sat, Mar 26, 2005 at 10:50:26PM +0000, Russell King wrote: > >>On Sat, Mar 26, 2005 at 09:41:41PM +0000, Matthew Wilcox wrote: >> >>>Any reason you can't merge ARM's options into the drivers/*/Kconfig (with >>>appropriate conditionals) and use drivers/Kconfig? >> >>Dunno. Haven't gotten around to sorting that out yet, and I don't >>particularly fancy trying to fight any corners over it. >> >>I think, a while back, it was thought to be better to keep ARM separate >>to keep the conditionals out of drivers/Kconfig. >> >>If the general concensus has changed, I might eventually sort it out if >>it causes enough trouble, or people think there's sufficient value to it. > > > As the original author of drivers/Kconfig, I think it's a brilliant > idea that everybody should use ;-) I haven't heard any dissenting > opinions yet. The only complaint I've heard is that net/Kconfig is now > under device drivers. I didn't make that change, and I agree it sucks.
This is likely a little OT for this thread, but I probably made that change (of grouping all networking options and drivers together). And I still think that they should all be grouped together -- whether it's under device drivers or a top-level Networking section.
The real problem AFAICT is that Networking options includes some protocols and then Network Device Support includes some other protocols. Maybe if there was a Network Protocol section things could be clearer. ??
-- ~Randy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |