public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: cmm@us.ibm.com
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: patch queue updated
Date: Wed, 10 Oct 2007 21:45:48 +0530	[thread overview]
Message-ID: <470CFAB4.8080408@linux.vnet.ibm.com> (raw)
In-Reply-To: <1192032053.3880.11.camel@localhost.localdomain>



Mingming Cao wrote:
> On Wed, 2007-10-10 at 17:35 +0530, Aneesh Kumar K.V wrote:
>> I have updated the patch queue at 
>>
>> http://www.radian.org/~kvaneesh/ext4/patch-series/
>>
>> http://www.radian.org/~kvaneesh/ext4/patch-series/ext4-patch-queue.tar
>>
>> Changes:
>> a) Add large-file-blocktype.patch  large-file.patch patch.
> 
> Could you send them out separately? I noticed that your queue is not
> based on the last ext4 patch queue. You modified mballoc-core.patch
> directly with large file block type changes...but your updated
> mballoc-core.patch doesn't have the latest proc fs fix from Ted. 
> 

It has the changes. http://www.radian.org/~kvaneesh/ext4/patch-series/mballoc-core.patch
I searched for PROC_FS . I did a git pull on patch queue before updating the patches.




> I would appreciate if you separete the largeblocktype changes for
> mballoc out of the core mballoc changes, as that patch is getting really
> big already.
> 
>> b) Add the stable-boundary-patch with dummy change
>> c) Add stable-boundary-undo.patch which undo the above dummy change.
> 
> The stable-boundary patch is being removed from ext4 patch queue,as some
> tools expect a meaning code diff to apply any patch.
> 

That is why i added a dummy change which is reverted by the later patch.



-aneesh

  reply	other threads:[~2007-10-10 16:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-10 12:05 patch queue updated Aneesh Kumar K.V
2007-10-10 16:00 ` Mingming Cao
2007-10-10 16:15   ` Aneesh Kumar K.V [this message]
2007-10-10 17:33     ` 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=470CFAB4.8080408@linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=cmm@us.ibm.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