From: Eric Paris <eparis@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk,
hch@infradead.org, alan@lxorguk.ukuu.org.uk,
sfr@canb.auug.org.au, john@johnmccutchan.com, rlove@rlove.org,
malware-list@lists.printk.net
Subject: Re: [PATCH -v1 03/11] fsnotify: add in inode fsnotify markings
Date: Tue, 17 Feb 2009 12:26:30 -0500 [thread overview]
Message-ID: <1234891590.19964.3.camel@localhost.localdomain> (raw)
In-Reply-To: <20090212135726.bbab736e.akpm@linux-foundation.org>
On Thu, 2009-02-12 at 13:57 -0800, Andrew Morton wrote:
> <picks a patch at random>
>
> I don't have a good sense of what value all of this work brings to
> Linux. Why should I get excited about this? Why is it all worth the
> time/effort/risk/etc which would be involved in getting it integrated?
>
> All rather unclear, but very important!
I have largely taken your comments and rewritten this patch (and a
couple others) to be easier to understand and review.
current patches are at http://people.redhat.com/~eparis/fsnotify
I received some offline comments which I intend to address and will be
reposting later this week.
thank you!
next prev parent reply other threads:[~2009-02-17 17:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 21:15 [PATCH -v1 01/11] fsnotify: unified filesystem notification backend Eric Paris
2009-02-09 21:15 ` [PATCH -v1 02/11] fsnotify: add group priorities Eric Paris
2009-02-09 21:15 ` [PATCH -v1 03/11] fsnotify: add in inode fsnotify markings Eric Paris
2009-02-12 21:57 ` Andrew Morton
2009-02-17 17:26 ` Eric Paris [this message]
2009-02-09 21:15 ` [PATCH -v1 04/11] fsnotify: parent event notification Eric Paris
2009-02-09 21:15 ` [PATCH -v1 05/11] dnotify: reimplement dnotify using fsnotify Eric Paris
2009-02-09 21:15 ` [PATCH -v1 06/11] fsnotify: generic notification queue and waitq Eric Paris
2009-02-09 21:15 ` [PATCH -v1 07/11] fsnotify: include pathnames with entries when possible Eric Paris
2009-02-09 21:16 ` [PATCH -v1 08/11] fsnotify: add correlations between events Eric Paris
2009-02-09 21:16 ` [PATCH -v1 09/11] fsnotify: fsnotify marks on inodes pin them in core Eric Paris
2009-02-09 21:16 ` [PATCH -v1 10/11] fsnotify: handle filesystem unmounts with fsnotify marks Eric Paris
2009-02-09 21:16 ` [PATCH -v1 11/11] inotify: reimplement inotify using fsnotify Eric Paris
2009-02-09 21:28 ` [PATCH -v1 00/11] fsnotify: unified filesystem notification backend 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=1234891590.19964.3.camel@localhost.localdomain \
--to=eparis@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hch@infradead.org \
--cc=john@johnmccutchan.com \
--cc=linux-kernel@vger.kernel.org \
--cc=malware-list@lists.printk.net \
--cc=rlove@rlove.org \
--cc=sfr@canb.auug.org.au \
--cc=viro@zeniv.linux.org.uk \
/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