From: Amy Griffis <amy.griffis@hp.com>
To: John McCutchan <john@johnmccutchan.com>, Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, Robert Love <rlove@rlove.org>
Subject: Re: [PATCH] inotify kernel API
Date: Sat, 27 May 2006 22:42:45 -0400 [thread overview]
Message-ID: <20060528024245.GA18625@zk3.dec.com> (raw)
In-Reply-To: <1148659946.7612.7.camel@localhost.localdomain>
John McCutchan wrote: [Fri May 26 2006, 12:12:26PM EDT]
> Having only glanced at your latest code, all of your changes and bug
> fixes look good. Thanks very much for putting the effort into auditing
> and testing inotify.
Thanks, that's great to hear.
Andrew, could this patch be included in the next -mm kernel?
Thanks,
Amy
next prev parent reply other threads:[~2006-05-28 2:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-26 2:10 [PATCH] inotify kernel API Amy Griffis
[not found] ` <1148659946.7612.7.camel@localhost.localdomain>
2006-05-26 16:12 ` John McCutchan
2006-05-28 2:42 ` Amy Griffis [this message]
2006-05-28 8:35 ` Arjan van de Ven
2006-05-28 15:49 ` Al Viro
2006-05-30 9:40 ` Andrew Morton
2006-05-30 13:51 ` 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=20060528024245.GA18625@zk3.dec.com \
--to=amy.griffis@hp.com \
--cc=akpm@osdl.org \
--cc=john@johnmccutchan.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlove@rlove.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