From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Jason Yan <yanaijie@huawei.com>
Cc: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] ext4: remove set but not used variable 'es' in ext4_jbd2.c
Date: Mon, 13 Apr 2020 21:56:16 -0400 [thread overview]
Message-ID: <20200414015616.GC90651@mit.edu> (raw)
In-Reply-To: <20200402034759.29957-1-yanaijie@huawei.com>
On Thu, Apr 02, 2020 at 11:47:59AM +0800, Jason Yan wrote:
> Fix the following gcc warning:
>
> fs/ext4/ext4_jbd2.c:341:30: warning: variable 'es' set but not used [-Wunused-but-set-variable]
> struct ext4_super_block *es;
> ^~
>
> Fixes: 2ea2fc775321 ("ext4: save all error info in save_error_info() and drop ext4_set_errno()")
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: Jason Yan <yanaijie@huawei.com>
Applied, thanks.
- Ted
prev parent reply other threads:[~2020-04-14 1:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 3:47 [PATCH -next] ext4: remove set but not used variable 'es' in ext4_jbd2.c Jason Yan
2020-04-14 1:56 ` Theodore Y. Ts'o [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=20200414015616.GC90651@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yanaijie@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;
as well as URLs for NNTP newsgroup(s).