From: Chris Mason <chris.mason@oracle.com>
To: sniper <s3c24xx@gmail.com>
Cc: Qinghuang Feng <qhfeng.kernel@gmail.com>,
linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: simplify iteration codes
Date: Fri, 16 Jan 2009 10:23:24 -0500 [thread overview]
Message-ID: <1232119404.21473.27.camel@think.oraclecorp.com> (raw)
In-Reply-To: <9bd6b5360901160720w3a2950eemaf2cd3e35caec788@mail.gmail.com>
On Fri, 2009-01-16 at 23:20 +0800, sniper wrote:
> On Fri, Jan 16, 2009 at 10:31 PM, Chris Mason <chris.mason@oracle.com> wrote:
> > On Fri, 2009-01-16 at 15:25 +0800, Qinghuang Feng wrote:
> >> merge list_for_each and list_entry to list_for_each_entry.
> >>
> >
> > Thanks, I've queued this up.
> >
> Good, but....
>
> Now I have made a new patch for cleanupping all the similar codes in btrfs.
> This patch has been tested in VM, it seems ok.
>
> Now should I rebuild another patch which based the previous patch,
> or could you be able to reverse the previous patch then I just post
> this new patch including all stuff?
>
> Sorry I am not much familiar with the posting flow, and I am not sure
> the meaning of "queued".
It means this one looks right and I've put it into my internal testing
tree. It should be in my next pull request.
But, I'll hold off on this one if there is a larger set of fixes coming
that contain it.
-chris
prev parent reply other threads:[~2009-01-16 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 7:25 [PATCH] Btrfs: simplify iteration codes Qinghuang Feng
2009-01-16 12:50 ` Qinghuang Feng
2009-01-16 14:31 ` Chris Mason
2009-01-16 15:20 ` sniper
2009-01-16 15:23 ` Chris Mason [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=1232119404.21473.27.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qhfeng.kernel@gmail.com \
--cc=s3c24xx@gmail.com \
/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