From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Theodore Tso <tytso@mit.edu>
Cc: cmm@us.ibm.com, sandeen@redhat.com, jack@suse.cz,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH 3/3] ext4: Add generic writepage callback
Date: Thu, 4 Jun 2009 11:58:44 +0530 [thread overview]
Message-ID: <20090604062844.GA26802@skywalker> (raw)
In-Reply-To: <20090603225308.GA21314@mit.edu>
On Wed, Jun 03, 2009 at 06:53:08PM -0400, Theodore Tso wrote:
> Hi Aneesh,
>
> In the future, *please* give me patches versus the patch queue. This
> patch moves functions around, so applying it is painful in the
> extreme, and it's very painful to check and see whether it undoes
> patches later in the patch.
I have done is against patch queue. After the stable patch. But I guess
some patches you added before the stable cause the patch apply to fail.
I have regenerated the patch and sent -v2 version. Also i split the
coding moving changes in to a new patch
>
> In fact, can you redo these patches (2/3 and 3/3), versus the latest
> in the patch queue?
>
Done. I sent you 4 patches which should be all you need to take.
-aneesh
next prev parent reply other threads:[~2009-06-04 6:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 15:58 [PATCH 1/3] ext4: Don't look at buffer_heads outside i_size Aneesh Kumar K.V
2009-05-27 15:58 ` [PATCH 2/3] ext4: Check for only delay or unwritten buffer_heads Aneesh Kumar K.V
2009-05-27 15:58 ` [PATCH 3/3] ext4: Add generic writepage callback Aneesh Kumar K.V
2009-05-28 8:33 ` Jan Kara
2009-06-03 22:53 ` Theodore Tso
2009-06-03 22:57 ` Theodore Tso
2009-06-04 6:28 ` Aneesh Kumar K.V [this message]
2009-05-28 8:27 ` [PATCH 2/3] ext4: Check for only delay or unwritten buffer_heads Jan Kara
2009-05-28 9:49 ` Aneesh Kumar K.V
2009-05-27 16:27 ` [PATCH 1/3] ext4: Don't look at buffer_heads outside i_size Josef Bacik
2009-05-28 8:21 ` Jan Kara
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=20090604062844.GA26802@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=cmm@us.ibm.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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).