From: Ted Ts'o <tytso@mit.edu>
To: Robin Dong <hao.bigrat@gmail.com>
Cc: linux-ext4@vger.kernel.org, Robin Dong <sanbai@taobao.com>
Subject: Re: [PATCH 2/2] ext4: fix a typo in struct ext4_allocation_context
Date: Mon, 31 Oct 2011 18:56:53 -0400 [thread overview]
Message-ID: <20111031225653.GA32161@thunk.org> (raw)
In-Reply-To: <1314272192-7414-2-git-send-email-hao.bigrat@gmail.com>
On Thu, Aug 25, 2011 at 07:36:32PM +0800, Robin Dong wrote:
> From: Robin Dong <sanbai@taobao.com>
>
> This patch change "bext" to "best".
>
> Signed-off-by: Robin Dong <sanbai@taobao.com>
Thanks, applied.
- Ted
next prev parent reply other threads:[~2011-10-31 22:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 11:36 [PATCH 1/2] ext4: remove redundant argument in mb_find_extent() Robin Dong
2011-08-25 11:36 ` [PATCH 2/2] ext4: fix a typo in struct ext4_allocation_context Robin Dong
2011-10-31 22:56 ` Ted Ts'o [this message]
2011-08-25 16:28 ` [PATCH 1/2] ext4: remove redundant argument in mb_find_extent() Andreas Dilger
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=20111031225653.GA32161@thunk.org \
--to=tytso@mit.edu \
--cc=hao.bigrat@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sanbai@taobao.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;
as well as URLs for NNTP newsgroup(s).