From: Mingming Cao <cmm@us.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: tytso@mit.edu, linux-ext4@vger.kernel.org
Subject: Re: ext4-mm-delalloc-ext4.patch
Date: Mon, 03 Mar 2008 15:12:44 -0800 [thread overview]
Message-ID: <1204585964.3636.20.camel@localhost.localdomain> (raw)
In-Reply-To: <20080303130823.ed6991a8.akpm@linux-foundation.org>
On Mon, 2008-03-03 at 13:08 -0800, Andrew Morton wrote:
> On Fri, 29 Feb 2008 09:26:36 -0800
> Mingming Cao <cmm@us.ibm.com> wrote:
>
> > On Fri, 2008-02-29 at 01:05 -0800, Andrew Morton wrote:
> > > generic_commit_write() is scheduled for removal in 2.6.26 and is
> > > removed already from -mm.
> > >
> > > Please switch to the new write_begin/write_end interface.
> >
> > I have a patch for that, sent to linux-ext4 last week. I will merge it
> > to the parent patch and update in ext4 patch queue.
> >
> > ext4: use write_begin/write_end in delalloc instead of prepare_write()
> > From: Mingming Cao <cmm@us.ibm.com>
>
> Thanks. But this change still isn't at
> ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/ext4-patches/LATEST/broken-out/,
> so ext4 is still a no-build for me.
>
Oh, sorry about the confusion. What I mean by "ext4 patch queue" is a
cutting edge ext4 development tree, which is not intend for mm or
upstream inclusion.
I have asked Ted this morning to update the "official" ext4 patch queue
at kernel.org, which is visiable to you and the world. I can't update it
myself.
Best regards,
Mingming
prev parent reply other threads:[~2008-03-03 23:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 9:05 ext4-mm-delalloc-ext4.patch Andrew Morton
2008-02-29 17:26 ` ext4-mm-delalloc-ext4.patch Mingming Cao
2008-03-03 21:08 ` ext4-mm-delalloc-ext4.patch Andrew Morton
2008-03-03 23:12 ` Mingming Cao [this message]
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=1204585964.3636.20.camel@localhost.localdomain \
--to=cmm@us.ibm.com \
--cc=akpm@linux-foundation.org \
--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