From: Mingming Cao <cmm@us.ibm.com>
To: tytso@mit.edu
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Ext4 patch queue updated(2.6.23-rc6)
Date: Thu, 20 Sep 2007 17:39:07 -0700 [thread overview]
Message-ID: <1190335147.5288.18.camel@localhost.localdomain> (raw)
In-Reply-To: <1189796613.3841.14.camel@localhost.localdomain>
http://repo.or.cz/w/ext4-patch-queue.git
Changes since last time
Updated uninit block group patch
Updated mballoc core patch
Update jbd cleanup patch
Removed large block support patch (as the 64k blk size rec_len overflow
patch might be updated later)
reordered serise file
Appreciate any testing!!
Ted,Please review and pull them to your git tree. Thanks
series
# Rebased the patches to 2.6.23-rc6
#
# Note the next two are in mm tree
jbd_slab_cleanup.patch
jbd_GFP_NOFAIL_flag_cleanup.patch
#below are not in mm tree
sparse-fix.patch
# Add unused inode watermark and checksum to blockgroup descriptors
# Need e2fsprogs changes to mkfs to use this featur
ext4_uninit_blockgroup.patch
#FLEX_BG
flex_bg_kernel.patch
####################################################
# unstable patches still have outstanding comments from lkml
####################################################
# Add journal checksums
ext4-journal_chksum-2.6.20.patch
ext4-journal-chksum-review-fix.patch
# inode verion patch series
# inode versioning is needed for NFSv4
# Need to address overwrite case and performance concerns
# Need to repost to lkml for comments before submit
#
# vfs changes, 64 bit inode->i_version
64-bit-i_version.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
# Export jbd stats through procfs
# Shall this move to debugfs?
# Still need to address akpm's comments.
jbd-stats-through-procfs
jbd-stats-through-procfs_fix.patch
####################################################
#Unstable patches
####################################################
# New delayed allocation patch
delalloc-vfs.patch
delalloc-ext4.patch
ext-truncate-mutex.patch
ext3-4-migrate.patch
new-extent-function.patch
###################################################
#mballoc
###################################################
generic-find-next-le-bit
mballoc-core.patch
next prev parent reply other threads:[~2007-09-21 0:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 0:30 ext4 patch queue updated(2.6.23-rc5) Mingming Cao
2007-09-13 14:58 ` Valerie Clement
2007-09-13 21:01 ` Mingming Cao
2007-09-14 19:03 ` Ext4 patch queue updated(2.6.23-rc6) Mingming Cao
2007-09-14 22:54 ` Andreas Dilger
2007-09-21 0:39 ` Mingming Cao [this message]
2007-09-27 1:36 ` Ext4 patch queue updated(2.6.23-rc8) Mingming Cao
2007-10-24 1:03 ` Ext4 patch queue updated(2.6.23-git17) 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=1190335147.5288.18.camel@localhost.localdomain \
--to=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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