From: Theodore Tso <tytso@mit.edu>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org, trivial@kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Andreas Dilger <adilger@sun.com>,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH 57/62] fs/ext4/mballoc.c: Remove unnecessary semicolons
Date: Sun, 5 Jul 2009 22:34:31 -0400 [thread overview]
Message-ID: <20090706023431.GF6706@mit.edu> (raw)
In-Reply-To: <d45c565b20589fe7884926b5174ef730de1c9442.1246173683.git.joe@perches.com>
On Sun, Jun 28, 2009 at 09:27:02AM -0700, Joe Perches wrote:
> Signed-off-by: Joe Perches <joe@perches.com>
Thanks, added to the ext4 patch queue.
- Ted
prev parent reply other threads:[~2009-07-06 2:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1246173664.git.joe@perches.com>
2009-06-28 16:27 ` [PATCH 57/62] fs/ext4/mballoc.c: Remove unnecessary semicolons Joe Perches
2009-07-06 2:34 ` 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=20090706023431.GF6706@mit.edu \
--to=tytso@mit.edu \
--cc=adilger@sun.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@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).