From: Borislav Petkov <bp@alien8.de>
To: Tony Luck <tony.luck@intel.com>
Cc: YueHaibing <yuehaibing@huawei.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-edac@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH -next] EDAC: Remove set but not used variable 'type'
Date: Tue, 25 Sep 2018 10:11:07 +0000 [thread overview]
Message-ID: <20180925101107.GA23986@zn.tnic> (raw)
In-Reply-To: <1537842964-109749-1-git-send-email-yuehaibing@huawei.com>
On Tue, Sep 25, 2018 at 02:36:04AM +0000, YueHaibing wrote:
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> drivers/edac/skx_edac.c: In function 'skx_mce_output_error':
> drivers/edac/skx_edac.c:949:8: warning:
> variable 'type' set but not used [-Wunused-but-set-variable]
>
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> ---
> drivers/edac/skx_edac.c | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/edac/skx_edac.c b/drivers/edac/skx_edac.c
> index b2987ef..3ffdbc4 100644
> --- a/drivers/edac/skx_edac.c
> +++ b/drivers/edac/skx_edac.c
> @@ -959,15 +959,11 @@ static void skx_mce_output_error(struct mem_ctl_info *mci,
> recoverable = GET_BITFIELD(m->status, 56, 56);
>
> if (uncorrected_error) {
> - if (ripv) {
> - type = "FATAL";
> + if (ripv)
> tp_event = HW_EVENT_ERR_FATAL;
> - } else {
> - type = "NON_FATAL";
> + else
> tp_event = HW_EVENT_ERR_UNCORRECTED;
> - }
> } else {
> - type = "CORRECTED";
> tp_event = HW_EVENT_ERR_CORRECTED;
> }
Looks like this @type thing was never used. Tony, did you want to use it
for something?
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2018-09-25 10:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 2:36 [PATCH -next] EDAC: Remove set but not used variable 'type' YueHaibing
2018-09-25 10:11 ` Borislav Petkov [this message]
2018-09-25 17:15 ` Luck, Tony
2018-10-04 10:49 ` YueHaibing
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=20180925101107.GA23986@zn.tnic \
--to=bp@alien8.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=tony.luck@intel.com \
--cc=yuehaibing@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