From: "Robert Love" <rlove@rlove.org>
To: "Amy Griffis" <amy.griffis@hp.com>
Cc: linux-kernel@vger.kernel.org,
"John McCutchan" <john@johnmccutchan.com>,
"Andrew Morton" <akpm@osdl.org>
Subject: Re: [PATCH] inotify: split kernel API from userspace support
Date: Thu, 1 Jun 2006 13:46:41 -0400 [thread overview]
Message-ID: <acdcfe7e0606011046y727c3e5aob478a408e29c7a0f@mail.gmail.com> (raw)
In-Reply-To: <20060601150702.GA2171@zk3.dec.com>
On 6/1/06, Amy Griffis <amy.griffis@hp.com> wrote:
> The following series of patches introduces a kernel API for inotify,
> making it possible for kernel modules to benefit from inotify's
> mechanism for watching inodes. With these patches, inotify will
> maintain for each caller a list of watches (via an embedded struct
> inotify_watch), where each inotify_watch is associated with a
> corresponding struct inode. The caller registers an event handler and
> specifies for which filesystem events their event handler should be
> called per inotify_watch.
Thank you for breaking the patch up. Looks good to me.
Acked-by: Robert Love <rml@novell.com>
Robert Love
next prev parent reply other threads:[~2006-06-01 17:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 15:07 Amy Griffis
2006-06-01 15:08 ` [PATCH 2/5] inotify: add name's inode to event handler Amy Griffis
2006-06-01 15:10 ` [PATCH 3/5] inotify: add interfaces to kernel API Amy Griffis
2006-06-01 15:10 ` [PATCH 4/5] inotify: allow watch removal from event handler Amy Griffis
2006-06-01 15:11 ` [PATCH 5/5] inotify: update kernel documentation Amy Griffis
2006-06-01 17:46 ` Robert Love [this message]
[not found] ` <1149216713.2865.0.camel@localhost.localdomain>
2006-06-02 2:51 ` [PATCH] inotify: split kernel API from userspace support John McCutchan
2006-06-02 12:32 ` Amy Griffis
2006-06-06 21:06 ` Pavel Machek
2006-06-08 3:59 ` Amy Griffis
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=acdcfe7e0606011046y727c3e5aob478a408e29c7a0f@mail.gmail.com \
--to=rlove@rlove.org \
--cc=akpm@osdl.org \
--cc=amy.griffis@hp.com \
--cc=john@johnmccutchan.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®