From: "J. Bruce Fields" <bfields@fieldses.org>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-fsdevel@vger.kernel.org, nfs@lists.sourceforge.net,
Neil Brown <neilb@suse.de>
Subject: Re: [NFS] [PATCH 00/19] export operations rewrite
Date: Fri, 14 Sep 2007 13:06:56 -0400 [thread overview]
Message-ID: <20070914170656.GF26622@fieldses.org> (raw)
In-Reply-To: <20070914170025.GA8594@lst.de>
On Fri, Sep 14, 2007 at 07:00:25PM +0200, Christoph Hellwig wrote:
> On Fri, Sep 14, 2007 at 12:43:55PM -0400, J. Bruce Fields wrote:
> > I'm hoping Neil can take a quick look as well (and make a response to
> > the comment on patch #1 along the way).
>
> The exportfs_d_alloc one? I have a patch for the done, I just need
> to run it through my testing setup before sending it out.
Oops, I meant #19, not #1--there's still a note addressed to Neil
sitting in there.
Typing faster than I was thinking, sorry--b.
next prev parent reply other threads:[~2007-09-14 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 11:47 [PATCH 00/19] export operations rewrite hch
2007-09-14 16:43 ` J. Bruce Fields
2007-09-14 17:00 ` Christoph Hellwig
2007-09-14 17:06 ` J. Bruce Fields [this message]
2007-09-28 2:09 ` Neil Brown
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=20070914170656.GF26622@fieldses.org \
--to=bfields@fieldses.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.