From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: zhong jiang <zhongjiang@huawei.com>
Cc: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ext4/mballoc: Remove unneeded variable "err"
Date: Sat, 4 Aug 2018 17:24:26 -0400 [thread overview]
Message-ID: <20180804212426.GE4461@thunk.org> (raw)
In-Reply-To: <1533380696-16325-1-git-send-email-zhongjiang@huawei.com>
On Sat, Aug 04, 2018 at 07:04:56PM +0800, zhong jiang wrote:
> The err is not used after initalization. So just remove the variable.
>
> Signed-off-by: zhong jiang <zhongjiang@huawei.com>
I'll apply this patch, but how did you generate the diff? The
function name here is all wrong:
> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
> index 8b24d3d..e29fce2 100644
> --- a/fs/ext4/mballoc.c
> +++ b/fs/ext4/mballoc.c
> @@ -3801,7 +3801,6 @@ static int ext4_mb_new_preallocation(struct ext4_allocation_context *ac)
^^^^^^^^^^^^^^^^^^^^^^^^^
The lines in question are from ext4_mb_release_inode_pa(), *not*
ext4_mb_new_preallocation(). So when I inspected the patch visually,
my first reaction was, "there's no way this patch would apply".
But then I looked at the C code changed by the patch, and I was
surprised to see that it applied correctly in a completely different
function, and when I regenerated the patch, the line numbers matched
yours --- so the only thing "wrong" in your patch is the function name.
So that raises the question --- how did you create the diff in this
patch? What version of git? And what version of the kernel?
Regards,
- Ted
next prev parent reply other threads:[~2018-08-04 21:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-04 11:04 [PATCH] ext4/mballoc: Remove unneeded variable "err" zhong jiang
2018-08-04 21:24 ` Theodore Y. Ts'o [this message]
2018-08-05 12:59 ` zhong jiang
2018-08-05 14:49 ` Theodore Y. Ts'o
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=20180804212426.GE4461@thunk.org \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhongjiang@huawei.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