I like that idea.
> this should also be a nice opportunity to introduce drivers/Config.in and
> remove even more duplication from arch/$ARCH/config.in. It comes of the
> cost of testing for the architecture, since e.g. s390 does not want to
> include most of drivers/*, but that means we'd actually collect this
> knowledge at a centralized place.
<gentle-irony>Oh no the dreaded unified arch tree!</gentle-irony>
Seriously, I think this is perhaps a bit brave in the short term.
> o The trivial patches moving statements like the above into the
> subsys/Config.in means that all of that file should be indented, which
> makes the patches look really large, even though they change very
I wouldn't be too worried about indentation, it's quite loosely followed
already. In fact better to do one patch that does the move and a second
larger but provably-trivial patch that fixes up the indentation.
> I have no strong opinion either way, but I'd certainly like
> a drivers/Config.in.
I think it's a great idea whose time has not yet come.
-- the price of civilisation today is a courageous willingness to prevail, with force, if necessary, against whatever vicious and uncomprehending enemies try to strike it down. - Roger Sandall, The Age, 28Sep2001. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/