Umm, the subsys part makes a lot of sense in terms of
logically separating the core of the kernel from the
architecture part and the subsystem part. While we
need a MM to complete a kernel, we certainly don't need
"subsys/sound/alsa/driver/es1371.c".
.
./arch
./fs
./init
./kernel
./lib
./mm
./include
./ipc
./subsys
./scripts
./Documentation
If this helps make the kernel source more like the modules
and devfs trees, then it makes even it more logically consistant.
Please remember that everyone who compiles a kernel is not
a uber kernel hacker. Average folks will appreciate some more
structure which helps to explain how things work.
>
> If, for some reason, we want to move all code in the kernel around
> we should do it once and in a planned mannor.
>
> Randomly introducing new and shiny naming schemes sucks. badly.
It's NOT random and it doesn't suck.
>
> Christoph
-- timothy.covell@ashavan.org. - 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/