From: Andrew Morton <akpm@linux-foundation.org>
To: Eric Paris <eparis@redhat.com>
Cc: linux-kernel@vger.kernel.org, sfr@canb.auug.org.au,
ttb@tentacle.dhs.org, rml@novell.com,
kosaki.motohiro@jp.fujitsu.com, zbr@ioremap.net,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] filesystem notification: create fs/notify to contain all fs notification
Date: Wed, 17 Dec 2008 15:06:13 -0800 [thread overview]
Message-ID: <20081217150613.bf787435.akpm@linux-foundation.org> (raw)
In-Reply-To: <20081217185941.2188.49536.stgit@paris.rdu.redhat.com>
On Wed, 17 Dec 2008 13:59:41 -0500
Eric Paris <eparis@redhat.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.
next prev parent reply other threads:[~2008-12-17 23:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 18:59 [PATCH] filesystem notification: create fs/notify to contain all fs notification Eric Paris
2008-12-17 19:26 ` Eric Paris
2008-12-17 23:06 ` Andrew Morton [this message]
2008-12-26 6:34 ` Al Viro
2008-12-17 23:13 ` Evgeniy Polyakov
2008-12-17 23:23 ` Eric Paris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081217150613.bf787435.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=eparis@redhat.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@novell.com \
--cc=sfr@canb.auug.org.au \
--cc=ttb@tentacle.dhs.org \
--cc=viro@zeniv.linux.org.uk \
--cc=zbr@ioremap.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox