From: tytso@mit.edu
To: Huang Weiyi <weiyi.huang@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH 6/6] ext4: remove unused #include <linux/version.h>
Date: Mon, 14 Dec 2009 09:26:06 -0500 [thread overview]
Message-ID: <20091214142606.GA8905@thunk.org> (raw)
In-Reply-To: <1260713198-1652-1-git-send-email-weiyi.huang@gmail.com>
On Sun, Dec 13, 2009 at 10:06:38PM +0800, Huang Weiyi wrote:
> Remove unused #include <linux/version.h>('s) in
> fs/ext4/block_validity.c
>
> Signed-off-by: Huang Weiyi <weiyi.huang@gmail.com>
> ---
> fs/ext4/block_validity.c | 1 -
> 1 files changed, 0 insertions(+), 1 deletions(-)
I was a tiny bit confused about why the subject line was 6/6; I assume
there were other related patches for different subsystems for patches
1-5?
I noticed that there was also an unused version.h #include'd in
fs/ext4/mballoc.h which I also removed at the same time.
Applied to the ext4 patch queue, thanks.
- Ted
prev parent reply other threads:[~2009-12-14 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-13 14:06 [PATCH 6/6] ext4: remove unused #include <linux/version.h> Huang Weiyi
2009-12-14 14:26 ` tytso [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=20091214142606.GA8905@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=weiyi.huang@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).