public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Paris <eparis@redhat.com>
To: Evgeniy Polyakov <zbr@ioremap.net>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	sfr@canb.auug.org.au, ttb@tentacle.dhs.org, rml@novell.com,
	kosaki.motohiro@jp.fujitsu.com
Subject: Re: [PATCH] filesystem notification: create fs/notify to contain all fs notification
Date: Wed, 17 Dec 2008 18:23:50 -0500	[thread overview]
Message-ID: <1229556230.3384.55.camel@localhost.localdomain> (raw)
In-Reply-To: <20081217231302.GC28283@ioremap.net>

[Dropping ttb@tentacle.dhs.org and rml@novell.com since their e-mails
were wrong in MAINTAINERS.  I sent them both requests to fix it.]

On Thu, 2008-12-18 at 02:13 +0300, Evgeniy Polyakov wrote:

> 
> Looks good, but what with the another patches in the series?

This can stand pretty well on its own and I figure if it gets into
2.6.29 everyone will at least be patching files on the right path.  I'm
hoping to have the complete inotify, dnotify, audit, and even fanotify
out and hopefully ready for 2.6.30.

Since this is reasonably useful today and I know others are looking at
inotify I figured I'd get it in as soon as possible so when I do try to
push all my crap that'll be the only conflict, not this moving of
files...

-Eric




      reply	other threads:[~2008-12-17 23:24 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
2008-12-26  6:34   ` Al Viro
2008-12-17 23:13 ` Evgeniy Polyakov
2008-12-17 23:23   ` Eric Paris [this message]

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=1229556230.3384.55.camel@localhost.localdomain \
    --to=eparis@redhat.com \
    --cc=akpm@linux-foundation.org \
    --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=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