From: "J. Bruce Fields" <bfields@fieldses.org>
To: Ben Myers <bpm@sgi.com>
Cc: linux-nfs@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH 0/2] commit_metadata export operation v6
Date: Sat, 20 Feb 2010 18:38:04 -0500 [thread overview]
Message-ID: <20100220233804.GA15015@fieldses.org> (raw)
In-Reply-To: <20100217200426.13409.32688.stgit@case>
On Wed, Feb 17, 2010 at 02:05:05PM -0600, Ben Myers wrote:
> Hey Bruce,
>
> Here is the latest version of the knfsd sync changes. I have addressed the
> suggestions provided by Christoph, Trond, Dave, and Alex.
>
> In this latest version I have fixed up the few nits in the nfsd patch that
> Christoph pointed out yesterday. I also have simplified the xfs patch as
> suggested by Dave.
Thanks, applying.
(Do you the second (xfs) patch to go in through the nfsd tree as well,
or should that go in through xfs maintainers after the nfsd merge?)
--b.
>
> Thanks,
> Ben
> ---
>
> Ben Myers (2):
> commit_metadata export operation replacing nfsd_sync_dir
> xfs_export_operations.commit_metadata
>
>
> fs/nfsd/nfs4recover.c | 4 --
> fs/nfsd/vfs.c | 106 ++++++++++++++++++++---------------------
> fs/xfs/linux-2.6/xfs_export.c | 20 ++++++++
> include/linux/exportfs.h | 5 ++
> 4 files changed, 78 insertions(+), 57 deletions(-)
>
> --
> Signature
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-02-20 23:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 20:05 [PATCH 0/2] commit_metadata export operation v6 Ben Myers
2010-02-17 20:05 ` [PATCH 1/2] commit_metadata export operation replacing nfsd_sync_dir Ben Myers
2010-02-17 20:05 ` [PATCH 2/2] xfs_export_operations.commit_metadata Ben Myers
2010-02-17 23:05 ` Dave Chinner
2010-02-19 10:31 ` [PATCH 0/2] commit_metadata export operation v6 Christoph Hellwig
2010-02-20 23:38 ` J. Bruce Fields [this message]
2010-02-22 19:53 ` bpm
2010-02-23 1:14 ` J. Bruce Fields
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=20100220233804.GA15015@fieldses.org \
--to=bfields@fieldses.org \
--cc=bpm@sgi.com \
--cc=linux-nfs@vger.kernel.org \
--cc=xfs@oss.sgi.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