From: Zheng Liu <gnehzuil.liu@gmail.com>
To: haiboliu6@gmail.com
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] change a comment on fs/ext4/extents.c
Date: Wed, 20 Jun 2012 23:51:25 +0800 [thread overview]
Message-ID: <20120620155125.GA14203@gmail.com> (raw)
In-Reply-To: <4fe09c5f.4ad3440a.5cc5.7bac@mx.google.com>
Hi Haibo,
If your patch only relates to ext4, please change the patch's subject
like this:
[PATCH] ext4: change a comment on fs/ext4/extents.c
On Tue, Jun 19, 2012 at 11:35:47PM +0800, haiboliu6@gmail.com wrote:
> From: HaiboLiu <HaiboLiu6@gmail.com>
>
> May be it's better.
Maybe the following commit log is better:
In this patch (197217a5), ext4_ext_try_to_merge has been changed to
merge an extent both left and right. So we need to update the comment
in here.
Regards,
Zheng
>
> Signed-off-by: HaiboLiu <HaiboLiu6@gmail.com>
> ---
> fs/ext4/extents.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
> index 74f23c2..db671b9 100644
> --- a/fs/ext4/extents.c
> +++ b/fs/ext4/extents.c
> @@ -1807,11 +1807,10 @@ has_space:
> nearex->ee_len = newext->ee_len;
>
> merge:
> - /* try to merge extents to the right */
> + /* try to merge extents */
> if (!(flag & EXT4_GET_BLOCKS_PRE_IO))
> ext4_ext_try_to_merge(inode, path, nearex);
>
> - /* try to merge extents to the left */
>
> /* time to correct all indexes above */
> err = ext4_ext_correct_indexes(handle, inode, path);
> --
> 1.7.9.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-06-20 15:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 15:35 [PATCH] change a comment on fs/ext4/extents.c haiboliu6
2012-06-20 15:51 ` Zheng Liu [this message]
2012-06-21 18:14 ` Haibo
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=20120620155125.GA14203@gmail.com \
--to=gnehzuil.liu@gmail.com \
--cc=haiboliu6@gmail.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).