linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mingming Cao <cmm@us.ibm.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ext4-patch-queue rebased to 2.6.22
Date: Mon, 09 Jul 2007 17:15:41 -0400	[thread overview]
Message-ID: <1184015741.3864.24.camel@localhost.localdomain> (raw)
In-Reply-To: <E1I7xBM-00044G-2v@candygram.thunk.org>

On Mon, 2007-07-09 at 13:37 -0400, Theodore Ts'o wrote:
> Per our discussion on the call, I've moved the fallocate patches back up
> to the front of the queue, and rebased the syscall numbers to 2.6.22.

I updated the ext4 patch queue.

It seem there is conflict to apply delayed allocation patch, fixed it.

Also I removed the ext4_no_inode_version mount option patch per our
discussion this morning.

At last, applied a few clean ups from Aneesh to the ext4 patch queue.

diff --git a/ext4-fallocate-1-syscall_i386_amd64_ppc
b/ext4-fallocate-1-syscall_i386_amd64_ppc
index 0f88bc9..91a8708 100644
--- a/ext4-fallocate-1-syscall_i386_amd64_ppc
+++ b/ext4-fallocate-1-syscall_i386_amd64_ppc
@@ -221,7 +221,7 @@ Index: linux-2.6.22-rc6/include/asm-x86_64/unistd.h
  __SYSCALL(__NR_timerfd, sys_timerfd)
  #define __NR_eventfd          284
  __SYSCALL(__NR_eventfd, sys_eventfd)
-+#define __NR_fallocate                284
++#define __NR_fallocate                285
 +__SYSCALL(__NR_fallocate, sys_fallocate)
  
  #ifndef __NO_STUBS
diff --git a/ext4-nanosecond-patch b/ext4-nanosecond-patch
index a8fb57e..e792cdd 100644
--- a/ext4-nanosecond-patch
+++ b/ext4-nanosecond-patch
@@ -3,7 +3,7 @@ From: Kalpak Shah <kalpak@clusterfs.com>
 This patch is a spinoff of the old nanosecond patches.

 It includes some cleanups and addition of a creation timestamp. The
-EXT3_FEATURE_RO_COMPAT_EXTRA_ISIZE flag has also been added along with
+EXT4_FEATURE_RO_COMPAT_EXTRA_ISIZE flag has also been added along with
 s_{min, want}_extra_isize fields in struct ext3_super_block.

 Signed-off-by: Andreas Dilger <adilger@clusterfs.com>
diff --git a/ext4_remove_subdirs_limit.patch
b/ext4_remove_subdirs_limit.patch
index effd545..83f4d5a 100644
--- a/ext4_remove_subdirs_limit.patch
+++ b/ext4_remove_subdirs_limit.patch
@@ -1,4 +1,4 @@
-From: kalpak@clusterfs.com Thu May 17 17:21:08 2007
+From: Kalpak Shah <kalpak@clusterfs.com>
 Hi,


> So we're just waiting for Amit to make the minor on-disk format change
> Andreas suggested before we push to Linus.

Yep.

Thanks,
Mingming

  reply	other threads:[~2007-07-10  0:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-09 17:37 ext4-patch-queue rebased to 2.6.22 Theodore Ts'o
2007-07-09 21:15 ` Mingming Cao [this message]
2007-07-10 14:54 ` Amit K. Arora
2007-07-10 17:09   ` Andreas Dilger
2007-07-10 17:55     ` Amit K. Arora
2007-07-10 20:26       ` Andreas Dilger

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=1184015741.3864.24.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).