From: Mingming Cao <cmm@us.ibm.com>
To: Kalpak Shah <kalpak@clusterfs.com>,
Jean noel Cordenner <jean-noel.cordenner@bull.net>
Cc: linux-ext4@vger.kernel.org
Subject: inode version updates
Date: Wed, 13 Jun 2007 18:02:42 -0700 [thread overview]
Message-ID: <1181782962.13428.26.camel@dyn9047017103.beaverton.ibm.com> (raw)
In-Reply-To: <466ED042.50401@linux.vnet.ibm.com>
On Tue, 2007-06-12 at 09:56 -0700, Avantika Mathur wrote:
> Ext4 Developer Interlock Call: Jun 11, 2007 Meeting Minutes
> i_version:
> - Kalpak will be separating i_version code from his expand-inode-size
> patch, and merging with the other i_version patches
>
I took out the i_version code from Kalpak's
ext4_expand_inode_extra_isize.patch.
http://repo.or.cz/w/ext4-patch-queue.git?
a=blob;f=ext4_i_version_hi_2.patch;h=4519dd6540a78cadd235dad68248456d59c3384c;hb=8b956b5c5ccc3731f23fbce8d036b21f378fbdec
Added Jean noel's inode version VFS patch and Ext4 patches. Now the full
inode version patch series can be found at ext4 patch queue:
# inode verion patch series
# inode versioning is needed for NFSv4
# vfs changes, 64 bit inode->i_version
i_version_update_vfs.patch
# reserve hi 32 bit inode version on ext4 on-disk inode
i_version_hi.patch
# ext4 inode version read/store
ext4_i_version_hi_2.patch
# ext4 inode version update
i_version_update_ext4.patch
Please Ack.
Thanks,
Mingming
next prev parent reply other threads:[~2007-06-14 1:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 16:56 Ext4 devel interlock meeting minutes (June 11, 2007) Avantika Mathur
2007-06-13 1:48 ` Jose R. Santos
2007-06-14 1:02 ` Mingming Cao [this message]
2007-06-14 9:53 ` inode version updates Andreas Dilger
2007-06-14 17:11 ` Mingming Cao
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=1181782962.13428.26.camel@dyn9047017103.beaverton.ibm.com \
--to=cmm@us.ibm.com \
--cc=jean-noel.cordenner@bull.net \
--cc=kalpak@clusterfs.com \
--cc=linux-ext4@vger.kernel.org \
/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