On Thu, 2006-08-24 at 14:00 +0100, David Howells wrote: > Make it possible to disable the block layer. Not all embedded devices require > it, some can make do with just JFFS2, NFS, ramfs, etc - none of which require > the block layer to be present. > > This patch does the following: > > (*) Introduces CONFIG_BLOCK to disable the block layer, buffering and blockdev > support. Excellent -- I've been meaning to do this (and occasionally hacking on it half-heartedly before getting distracted by something else shiny) for a _long_ time. It looks good in general. > (*) The contents of a number of filesystem- and blockdev-specific header files > are now contingent on their own configuration options. This includes: > Ext3/JBD, RAID, MSDOS and ReiserFS. Why? Those header files shouldn't be included from anywhere _but_ the code in question, and in fact should probably be just moved into fs/foo instead of living in include/linux/foo_fs.h. And please, _never_ make anything dependent on CONFIG_foo_MODULE. -- dwmw2 - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
