From: Theodore Tso <tytso@mit.edu>
To: Akira Fujita <a-fujita@rs.jp.nec.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [RFC][PATCH 1/3] Add EXT4_IOC_MOVE_EXT ioctl and related functions
Date: Wed, 17 Jun 2009 20:12:39 -0400 [thread overview]
Message-ID: <20090618001239.GH7867@mit.edu> (raw)
In-Reply-To: <4A388462.9070209@rs.jp.nec.com>
On Wed, Jun 17, 2009 at 02:51:30PM +0900, Akira Fujita wrote:
> Hi Ted,
>
> Theodore Tso wrote:
> > As a side note, the static functions in fs/ext4/move_extent.c really
> > don't need the ext4_mext prefix, since static functions don't have
> > namespace issues that require a consistent naming scheme. (Sometimes
> > a shorter name can also be useful since it avoids needing to line wrap
> > function calls with a long list of parameters.)
>
> This patch is for "online-defrag" in the ext4 patch queue,
> and changes are as follows:
>
> - Remove unneeded function prefix (ext4_mext_ or ext4_)
> in fs/ext4/move_extent.c to make function name shorter.
> And change some name of functions.
> - Fix error handling issue.
> - Add some argument checks.
>
> If this patch does not seem to have any problem,
> could you add this change to the ext4 patch queue?
Thanks for your patch; I've folded your improvements changes into the
online-defrag patch in the ext4 patch queue.
Best regards,
- Ted
prev parent reply other threads:[~2009-06-18 0:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 7:06 [RFC][PATCH 1/3] Add EXT4_IOC_MOVE_EXT ioctl and related functions Akira Fujita
2009-06-13 13:21 ` Theodore Tso
2009-06-15 8:03 ` Akira Fujita
2009-06-17 5:51 ` Akira Fujita
2009-06-18 0:12 ` 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=20090618001239.GH7867@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).