From: Theodore Ts'o <tytso@mit.edu>
To: Zhao Hongjiang <zhaohongjiang37@gmail.com>
Cc: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ext4: get rid of the duplicate code on ext4_fill_super
Date: Thu, 8 Nov 2012 12:14:17 -0500 [thread overview]
Message-ID: <20121108171417.GC19977@thunk.org> (raw)
In-Reply-To: <508E30F8.3090606@gmail.com>
On Mon, Oct 29, 2012 at 03:32:08PM +0800, Zhao Hongjiang wrote:
> From: Zhao Hongjiang <zhaohongjiang@huawei.com>
>
> Clean the duplicate code on ext4_fill_super cause the bellow
> also have it.
>
> Signed-off-by: Zhao Hongjiang <zhaohongjiang@huawei.com>
Applied, thanks!
I used the commit description:
ext4: get rid of redundant code in ext4_fill_super()
- Ted
prev parent reply other threads:[~2012-11-08 22:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 7:32 [PATCH] ext4: get rid of the duplicate code on ext4_fill_super Zhao Hongjiang
2012-11-08 17:14 ` Theodore Ts'o [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=20121108171417.GC19977@thunk.org \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhaohongjiang37@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;
as well as URLs for NNTP newsgroup(s).