From: Theodore Tso <tytso@mit.edu>
To: Akira Fujita <a-fujita@rs.jp.nec.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH 4/4]ext4: Fix comment typo in move_extent.c
Date: Tue, 10 Nov 2009 16:56:12 -0500 [thread overview]
Message-ID: <20091110215612.GF13262@mit.edu> (raw)
In-Reply-To: <4AEA98D0.5070602@rs.jp.nec.com>
On Fri, Oct 30, 2009 at 04:42:08PM +0900, Akira Fujita wrote:
> ext4: Fix comment typo in move_extent.c
>
> From: Akira Fujita <a-fujita@rs.jp.nec.com>
Thanks, I've added this to the ext4 patch queue, but with the
following updated commit description:
ext4: Fix spelling typos in move_extent.c
From: Akira Fujita <a-fujita@rs.jp.nec.com>
Fix a few spelling typos in move_extent.c
Signed-off-by: Akira Fujita <a-fujita@rs.jp.nec.co.jp>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
prev parent reply other threads:[~2009-11-10 21:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 7:42 [PATCH 4/4]ext4: Fix comment typo in move_extent.c Akira Fujita
2009-11-10 21:56 ` Theodore Tso [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=20091110215612.GF13262@mit.edu \
--to=tytso@mit.edu \
--cc=a-fujita@rs.jp.nec.com \
--cc=linux-ext4@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).