From: Anand Avati <avati@gluster.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: muirj@nortel.com, csaba@gluster.com,
fuse-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, dl-hacking@gluster.com
Subject: Re: [PATCH] fuse: cache invalidation calls
Date: Wed, 3 Jun 2009 07:51:44 -0500 (CDT) [thread overview]
Message-ID: <1119562997.1044731244033504415.JavaMail.root@mb1> (raw)
In-Reply-To: <683929306.1044151244033426071.JavaMail.root@mb1>
----- "Miklos Szeredi" <miklos@szeredi.hu> wrote:
> John, thanks for the patch. If no problems are found I'd like to add
> it to the 2.6.31 queue.
>
> Csaba, Anand, does this meet your requirements?
>
> Other comments?
I was wondering how the userland libfuse would be made aware of the presence of these two notification features?
Avati
next parent reply other threads:[~2009-06-03 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <683929306.1044151244033426071.JavaMail.root@mb1>
2009-06-03 12:51 ` Anand Avati [this message]
2009-06-04 9:22 ` [PATCH] fuse: cache invalidation calls Miklos Szeredi
2009-06-04 9:32 ` Csaba Henk
2009-06-04 9:35 ` Miklos Szeredi
2009-06-03 8:01 Miklos Szeredi
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=1119562997.1044731244033504415.JavaMail.root@mb1 \
--to=avati@gluster.com \
--cc=csaba@gluster.com \
--cc=dl-hacking@gluster.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=muirj@nortel.com \
/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;
as well as URLs for NNTP newsgroup(s).