From: <Nicolas.Ferre@microchip.com>
To: <yuehaibing@huawei.com>, <herbert@gondor.apana.org.au>,
<davem@davemloft.net>, <alexandre.belloni@bootlin.com>,
<Ludovic.Desroches@microchip.com>, <Tudor.Ambarus@microchip.com>
Cc: <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-crypto@vger.kernel.org>
Subject: Re: [PATCH -next] crypto: atmel - remove set but not used variable 'alg_name'
Date: Wed, 24 Apr 2019 08:55:10 +0000 [thread overview]
Message-ID: <0d8312a8-289e-71ea-3b20-c2e5c1ef47d6@microchip.com> (raw)
In-Reply-To: <20190424075352.22828-1-yuehaibing@huawei.com>
On 24/04/2019 at 09:53, Yue Haibing wrote:
> From: YueHaibing <yuehaibing@huawei.com>
>
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> drivers/crypto/atmel-tdes.c: In function 'atmel_tdes_setkey':
> drivers/crypto/atmel-tdes.c:803:14: warning: variable 'alg_name' set but not used [-Wunused-but-set-variable]
>
> It is not used any more since
> commit 52ea3cd2917b ("crypto: atmel - Forbid 2-key 3DES in FIPS mode")
>
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
Looks good to me:
Reviewed-by: Nicolas Ferre <nicolas.ferre@microchip.com>
> ---
> drivers/crypto/atmel-tdes.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/crypto/atmel-tdes.c b/drivers/crypto/atmel-tdes.c
> index 12492d9..fa76620 100644
> --- a/drivers/crypto/atmel-tdes.c
> +++ b/drivers/crypto/atmel-tdes.c
> @@ -800,12 +800,9 @@ static int atmel_tdes_setkey(struct crypto_ablkcipher *tfm, const u8 *key,
> unsigned int keylen)
> {
> struct atmel_tdes_ctx *ctx = crypto_ablkcipher_ctx(tfm);
> - const char *alg_name;
> u32 flags;
> int err;
>
> - alg_name = crypto_tfm_alg_name(crypto_ablkcipher_tfm(tfm));
> -
> flags = crypto_ablkcipher_get_flags(tfm);
> err = __des3_verify_key(&flags, key);
> if (unlikely(err)) {
>
--
Nicolas Ferre
next prev parent reply other threads:[~2019-04-24 8:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 7:53 Yue Haibing
2019-04-24 8:55 ` Nicolas.Ferre [this message]
2019-04-25 7:18 ` Tudor.Ambarus
2019-05-03 6:09 ` Herbert Xu
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=0d8312a8-289e-71ea-3b20-c2e5c1ef47d6@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®