From: Chris Mason <chris.mason@oracle.com>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/5] btrfs: trivial cleanups
Date: Thu, 02 Apr 2009 13:23:18 -0400 [thread overview]
Message-ID: <1238692998.29739.14.camel@think.oraclecorp.com> (raw)
In-Reply-To: <20090402021426.180324740@intel.com>
On Thu, 2009-04-02 at 10:14 +0800, Wu Fengguang wrote:
> Hi Mason,
>
> I accumulated some trivial patches while reading the btrfs code.
> Please take the ones that you are OK with :-)
Thanks for sending these along (and reading the code) I took #1 and #3.
I'm trying to avoid lots of whitespace churn right now, and I like the
dir parameter name ;)
-chris
>
> [PATCH 1/5] btrfs: reduce pointer dereference chains
> [PATCH 2/5] btrfs: use meaningful parameter names
> [PATCH 3/5] btrfs: fix typos in comments
> [PATCH 4/5] btrfs: lineup macros
> [PATCH 5/5] btrfs: lineup objectid macros
>
> Thanks,
> Fengguang
parent reply other threads:[~2009-04-02 17:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20090402021426.180324740@intel.com>]
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=1238692998.29739.14.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=fengguang.wu@intel.com \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).