From: Mingming Cao <cmm@us.ibm.com>
To: tytso@mit.edu
Cc: linux-ext4@vger.kernel.org
Subject: ext4 patch queue updated
Date: Tue, 17 Jul 2007 13:44:41 -0700 [thread overview]
Message-ID: <1184705081.3820.10.camel@localhost.localdomain> (raw)
In-Reply-To: <1184699323.3820.3.camel@localhost.localdomain>
Hi Ted,
The ext4 patch queue has been updated with updates to address latest
review comments. http://repo.or.cz/w/ext4-patch-queue.git
The series is being reordered: the patches still has outstanding
comments are moved to the end of the series. Per our discussion on
Monday, tThose patches are ready for submission are
# Rebased the patches to 2.6.22
# fallocate() syscall patches and ext4 fallocate() implementation
# Missing manpages
#ext4-fallocate-1-man-page
ext4-fallocate-2-syscall_i386_amd64_ppc
ext4-fallocate-3-ext4_support
ext4-fallocate-4-uninit_write_support
ext4-fallocate-5-new-ondisk-format
# Add mount option to turn off extents
ext4_noextent_mount_opt.patch
# Mounted ext4dev fs with extents by default for testing purpose,
# for Ext4 product release, extents mount option
# will be turn on only if the fs has EXTENTS feature on
ext4_extents_on_by_default.patch
# Propagate inode flags
ext4-propagate_flags.patch
# Add extent sanity checks
ext4-extent-sanity-checks.patch
# Bug fix:set 64bit JBD2 feature on >32bit ext4 fs
ext4_set_jbd2_64bit_feature.patch
# Fix: Rename CONFIG_JBD_DEBUG to CONFIG_JBD2_DEBUG
jbd2_config_jbd2_debug_fix.patch
# Export jbd2-debug via debugfs
jbd2_move_jbd2_debug_to_debugfs.patch
# Nanosecond timestamp support
ext4-nanosecond-patch
ext4_negative_timestamp_handle_fix.patch
# New patch to expand inode i_extra_isize to support features
# in high part of inode (>128 bytes)
ext4_expand_inode_extra_isize.patch
# Remove 32000 subdirs limit.
ext4_remove_subdirs_limit.patch
# Various Cleanups
ext4-zero_user_page.patch
is_power_of_2-ext4-superc.patch
ext4-remove-extra-is_rdonly-check.patch
ext4_extent_compilation_fixes.patch
ext4_extent_macros_cleanup.patch
#JBD->JBD2 naming cleanups
next prev parent reply other threads:[~2007-07-17 20:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-01 7:36 [EXT4 set 3][PATCH 1/1] ext4 nanosecond timestamp Mingming Cao
2007-07-03 6:37 ` Aneesh Kumar K.V
2007-07-03 10:28 ` Kalpak Shah
2007-07-04 3:32 ` Mingming Cao
2007-07-04 6:36 ` Aneesh Kumar K.V
2007-07-04 7:24 ` Aneesh Kumar K.V
2007-07-04 16:44 ` Andreas Dilger
2007-07-03 10:41 ` Kalpak Shah
2007-07-10 23:30 ` Andrew Morton
2007-07-11 2:00 ` Mingming Cao
2007-07-11 11:14 ` Andreas Dilger
2007-07-11 11:28 ` Andreas Dilger
2007-07-12 12:58 ` Kalpak Shah
2007-07-13 4:29 ` Aneesh Kumar K.V
2007-07-13 7:05 ` Kalpak Shah
2007-07-13 21:46 ` Mingming Cao
2007-07-17 0:49 ` Mingming Cao
2007-07-17 9:59 ` Kalpak Shah
2007-07-17 19:08 ` Mingming Cao
2007-07-17 20:44 ` Mingming Cao [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-01 7:36 [EXT4 set 2][PATCH 5/5] cleanups: Export jbd2-debug via debugfs Mingming Cao
2007-07-10 23:30 ` Andrew Morton
2007-07-16 8:19 ` [PATCH 1/1] ext4: JBD->JBD2 naming cleanups Mingming Cao
2007-07-16 14:56 ` ext4 patch queue updated Mingming Cao
2007-06-13 20:20 Mingming Cao
2007-06-15 5:13 ` Alex Tomas
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=1184705081.3820.10.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;
as well as URLs for NNTP newsgroup(s).