From: Mingming Cao <cmm@us.ibm.com>
To: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
Cc: Theodore Tso <tytso@mit.edu>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: cleaned up ext4 patch series
Date: Mon, 19 Mar 2007 09:15:22 -0800 [thread overview]
Message-ID: <1174324522.11657.14.camel@localhost.localdomain> (raw)
In-Reply-To: <1174319308.11636.8.camel@kleikamp.austin.ibm.com>
On Mon, 2007-03-19 at 10:48 -0500, Dave Kleikamp wrote:
> Ted,
> I have rebased the ext4 patchset on 2.6.21-rc4 and cleaned up some bad
> whitespace and sparse warnings. The patches are here:
> http://www.kernel.org/pub/linux/kernel/people/shaggy/ext4/ext4-2007-03-19.tar.bz2
> Untarred here:
> http://www.kernel.org/pub/linux/kernel/people/shaggy/ext4/ext4-2007-03-19/
>
> I have commented the series file with the changes I've made. Some of
> the patches are missing signed-of-by:
>
> # Rebased the patches to 2.6.21-rc4
>
> # New patch to fix whitespace before applying new patches
> whitespace.patch
>
> # Replaced truncated beginning comments
> extent-overlap-bugfix
>
> persistent_allocation_1_ioctl_and_unitialized_extents
>
We could mention here that this patch is going to be replaced by a new
patch to use the fallocate() operations.
> # Fixed an endian error
> persistent_allocation_2_support_for_writing_to_unitialized_extent
>
I think Amit has an updated version of this patch in his place.
> # Note: still lots of outstanding comments from linux-ext4 list, 12/2006
> # Missing signed-off-by:
> booked-page-flag.patch
>
> # Missing signed-off-by:
> ext4-block-reservation.patch
>
> # fixed a bunch of endianness errors reported by sparse
> # Needs a signed-off-by from Alex, then can add shaggy's
> ext4-delayed-allocation.patch
>
> ext4-delalloc-extents-48bit.patch
>
> # updated to latest version
> nanosecond_timestamps.patch
>
This nanosecond patch could be move to upstream earlier than the delayed
allocation patch (Alex is working to rewrite it at VFS level), so shall
we move it before the booked-page-flag.patch?
I wonder if we should create two branches: one branch for patches that
are well discussed and tested, which Andrew could trust and pull to mm
tree; and create another branch to store patches that are still under
discussion and likely to be rewriten based on the review feedback.
Thanks,
Mingming
next prev parent reply other threads:[~2007-03-19 17:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 15:48 cleaned up ext4 patch series Dave Kleikamp
2007-03-19 17:15 ` Mingming Cao [this message]
2007-03-19 17:31 ` Andreas Dilger
2007-03-21 12:19 ` [Patch 0/2] Persistent preallocation in ext4 (using fallocate inode op) Amit K. Arora
2007-03-21 12:31 ` [Patch 1/2] preallocation patch " Amit K. Arora
2007-03-21 12:35 ` [Patch 2/2] write support for uninitialized extents Amit K. Arora
2007-03-19 19:42 ` cleaned up ext4 patch series Theodore Tso
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=1174324522.11657.14.camel@localhost.localdomain \
--to=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=shaggy@linux.vnet.ibm.com \
--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).