[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20081217150613.bf787435.akpm@linux-foundation.org>
Date: Wed, 17 Dec 2008 15:06:13 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Eric Paris <eparis@...hat.com>
Cc: linux-kernel@...r.kernel.org, sfr@...b.auug.org.au,
ttb@...tacle.dhs.org, rml@...ell.com,
kosaki.motohiro@...fujitsu.com, zbr@...emap.net,
Al Viro <viro@...iv.linux.org.uk>
Subject: Re: [PATCH] filesystem notification: create fs/notify to contain
all fs notification
On Wed, 17 Dec 2008 13:59:41 -0500
Eric Paris <eparis@...hat.com> wrote:
> Creating a generic filesystem notification interface, fsnotify, which will be
> used by inotify, dnotify, and eventually fanotify is really starting to
> clutter the fs directory. This patch simply moves inotify and dnotify into
> fs/notify/inotify and fs/notify/dnotify respectively to make both current fs/
> and future notification tidier.
>
I have no objections.
> ---
>
> fs/Kconfig | 39 --
> fs/Makefile | 5
> fs/dnotify.c | 194 --------
> fs/inotify.c | 913 --------------------------------------
> fs/inotify_user.c | 778 --------------------------------
> fs/notify/Kconfig | 2
> fs/notify/Makefile | 2
> fs/notify/dnotify/Kconfig | 10
> fs/notify/dnotify/Makefile | 1
> fs/notify/dnotify/dnotify.c | 194 ++++++++
> fs/notify/inotify/Kconfig | 27 +
> fs/notify/inotify/Makefile | 2
> fs/notify/inotify/inotify.c | 913 ++++++++++++++++++++++++++++++++++++++
> fs/notify/inotify/inotify_user.c | 778 ++++++++++++++++++++++++++++++++
> 14 files changed, 1931 insertions(+), 1927 deletions(-)
But I don't want to carry the patch in -mm - I'm not well set up for
large file movement patches and they're a pita to carry.
git does a good job of this and perhaps we can persuade Al to carry
this patch in the vfs tree. Otherwise I'd suggest that you send it in
to Linus lateish in the 2.6.29-rc1 merge window. Please remember to cc
me on that email.
--
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