From: hch@lst.de
To: linux-fsdevel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: [PATCH 00/19] export operations rewrite
Date: Fri, 14 Sep 2007 13:47:46 +0200 [thread overview]
Message-ID: <20070914114746.GA28282@lst.de> (raw)
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.
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.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2007-09-14 11:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 11:47 hch [this message]
2007-09-14 16:43 ` [PATCH 00/19] export operations rewrite 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
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=20070914114746.GA28282@lst.de \
--to=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 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.