From: Neil Brown <neilb@suse.de>
To: hch@lst.de, akpm@linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: [PATCH 00/19] export operations rewrite
Date: Fri, 28 Sep 2007 12:09:56 +1000 [thread overview]
Message-ID: <18172.25204.554112.418896@notabene.brown> (raw)
In-Reply-To: message from hch@lst.de on Friday September 14
On Friday September 14, hch@lst.de wrote:
> This patchset is a medium scale rewrite of the export operations
> interface. The goal is to make the interface less complex, and
> easier to understand from the filesystem side, aswell as preparing
> generic support for exporting of 64bit inode numbers.
These 19 patches
Acked-by: NeilBrown <neilb@suse.de>
I didn't do a very thorough review this time, but I did the previous
time, and the one problem I found (module dependencies) has been
addressed - Thanks.
NeilBrown
>
> This touches all nfs exporting filesystems, and I've done testing
> on all of the filesystems I have here locally (xfs, ext2, ext3, reiserfs,
> jfs)
>
> Compared to the last version I've fixed the white space issues that
> checkpatch.pl complained about.
>
> Note that this patch series is against mainline. There will be some
> xfs changes landing in -mm soon that revamp lots of the code touched
> here. They should hopefully include the first path in the series so
> it can be simply dropped, but the xfs conversion will need some smaller
> updates. I will send this update as soon as the xfs tree updates get
> pulled into -mm.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2007-09-28 2:10 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 ` [NFS] " J. Bruce Fields
2007-09-28 2:09 ` Neil Brown [this message]
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=18172.25204.554112.418896@notabene.brown \
--to=neilb@suse.de \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--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 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).