From: Theodore Ts'o <tytso@mit.edu>
To: "gnehzuil.liu@gmail.com" <gnehzuil.liu@gmail.com>
Cc: linux-ext4@vger.kernel.org, Zheng Liu <wenqing.lz@taobao.com>
Subject: Re: [PATCH] ext4: remove duplicated declarations in inode.c
Date: Sun, 19 Aug 2012 18:10:00 -0400 [thread overview]
Message-ID: <20120819221000.GA25738@thunk.org> (raw)
In-Reply-To: <1338987802-10186-1-git-send-email-gnehzuil.liu@gmail.com>
On Wed, Jun 06, 2012 at 09:03:22PM +0800, gnehzuil.liu@gmail.com wrote:
> From: Zheng Liu <wenqing.lz@taobao.com>
>
> in patch cb20d5188366f04d96d2e07b1240cc92170ade40, ext4_set_bh_endio and
> ext4_end_io_buffer_write are declared at the beginning of inode.c file. So we
> can remove duplicated declarations in this file.
>
> Signed-off-by: Zheng Liu <wenqing.lz@taobao.com>
Applied, applied.
- Ted
prev parent reply other threads:[~2012-08-19 22:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 13:03 [PATCH] ext4: remove duplicated declarations in inode.c gnehzuil.liu
2012-08-19 22:10 ` 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=20120819221000.GA25738@thunk.org \
--to=tytso@mit.edu \
--cc=gnehzuil.liu@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=wenqing.lz@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).