> > The next step is to split up fs.h some more, as some things are
> > including it for trivial bits, but sucking in things like the superblock
> > includes for every fs. I've already started this by moving ERR_PTR and
> > friends into <linux/err.h>
>
> Just checking - you realize that getting the super_block includes out of fs.h
> is easy, right? In fact I already did it in my Unbork fs.h (1..4) set of
> patches last month
Ah yes, I had forgotten about that thread. I'll go look through
the archives later today, to make sure I don't duplicate any work
already done 8-)
>, at least I set a pattern using ext2 as an example, which
> is trivially extended for al filesystems. Now, I'm just waiting for one of
> two things to happen: Al to decide he's finished mucking around in there and
> I can submit the patch to Linus, or Al will feel threatened again and submit
> a similar patch to Linus.
Matthew Wilcox came up with a suggestion of fs.h fathering an inode.c
which may not be an entirely bad idea given how many files pull in
fs.h just for the inode definition, but don't need any of the fluff
that goes along with it.
The patch I posted yesterday still has 1-2 flaws (I introduced
two circular dependancies in fs.h Ahem, frighteningly easy to do
unless you keep generating the graphs and looking what changed)
I'll fix it up, and post a corrected version tonight sometime.
> I just find it much easier to work with and feel
> better about it when the kernel doesn't doesn't have its thumb tied to its
> nose.
Nice choice of words. Quite.
-- | Dave Jones. http://www.codemonkey.org.uk | SuSE Labs - 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/