[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0802231949070.15223@blonde.site>
Date: Sat, 23 Feb 2008 19:55:27 +0000 (GMT)
From: Hugh Dickins <hugh@...itas.com>
To: Al Viro <viro@...IV.linux.org.uk>
cc: Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, Christoph Hellwig <hch@....de>,
Greg KH <gregkh@...e.de>, David Howells <dhowells@...hat.com>
Subject: Re: [RFC 03/11] slim down debugfs
On Sat, 23 Feb 2008, Al Viro wrote:
> On Tue, Feb 19, 2008 at 05:04:38AM +0100, Arnd Bergmann wrote:
> > With most of debugfs now copied to generic code in libfs,
> > we can remove the original copy and replace it with thin
> > wrappers around libfs.
> >
> > Signed-off-by: Arnd Bergmann <arnd@...db.de>
> > Index: linux-2.6/fs/Kconfig
> > ===================================================================
> > --- linux-2.6.orig/fs/Kconfig
> > +++ linux-2.6/fs/Kconfig
> > @@ -1001,6 +1001,14 @@ config CONFIGFS_FS
> > Both sysfs and configfs can and should exist together on the
> > same system. One is not a replacement for the other.
> >
> > +config LIBFS
> > + tristate
> > + default m
> > + help
> > + libfs is a helper library used by many of the simpler file
> > + systems. Parts of libfs can be modular when all of its users
> > + are modules as well, and the users should select this symbol.
>
> NAK. For one thing, you need dependencies or selects and none of the
> patches later in the series introduces them. For another, neither
> dependencies nor selects work well if you have non-modular users of
> that sucker. Seriously, try to add those and do allmodconfig. Then
> look what a mess it produces.
For sure. Luckily, ramfs makes extensive use of simple_ libfs functions
(ramfs is where they came from originally), and is always configured in,
so libfs should always be in (unless Arnd's patches change things around
and ramfs no longer uses it).
Hugh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists