From: Austin Kim <austindh.kim@gmail•com>
To: herbert@gondor•apana.org.au, davem@davemloft•net,
catalin.marinas@arm•com, will@kernel•org,
john.johansen@canonical•com, jmorris@namei•org, serge@hallyn•com
Cc: linux-kernel@vger•kernel.org,
linux-arm-kernel@lists•infradead.org,
linux-security-module@vger•kernel.org,
linux-crypto@vger•kernel.org, austindh.kim@gmail•com,
austin.kim@lge•com
Subject: [PATCH] crypto: arm64/gcm - remove Wunused-const-variable ghash_cpu_feature
Date: Thu, 27 May 2021 07:28:09 +0100 [thread overview]
Message-ID: <20210527062809.GA1251@raspberrypi> (raw)
GCC compiler complains with below messages.
warning: ‘ghash_cpu_feature’ defined but not used [-Wunused-const-variable=]
static const struct cpu_feature ghash_cpu_feature[] = {
^~~~~~~~~~~~~~~~~
The variable with MODULE_DEVICE_TABLE() is registered as platform_driver.
But ghash_cpu_feature is not used, so remove ghash_cpu_feature.
Signed-off-by: Austin Kim <austindh.kim@gmail•com>
---
arch/arm64/crypto/ghash-ce-glue.c | 5 -----
1 file changed, 5 deletions(-)
diff --git a/arch/arm64/crypto/ghash-ce-glue.c b/arch/arm64/crypto/ghash-ce-glue.c
index 720cd3a58da3..c3f27d0d5329 100644
--- a/arch/arm64/crypto/ghash-ce-glue.c
+++ b/arch/arm64/crypto/ghash-ce-glue.c
@@ -615,10 +615,5 @@ static void __exit ghash_ce_mod_exit(void)
crypto_unregister_shash(&ghash_alg);
}
-static const struct cpu_feature ghash_cpu_feature[] = {
- { cpu_feature(PMULL) }, { }
-};
-MODULE_DEVICE_TABLE(cpu, ghash_cpu_feature);
-
module_init(ghash_ce_mod_init);
module_exit(ghash_ce_mod_exit);
--
2.20.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-05-27 6:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 6:28 Austin Kim [this message]
2021-05-27 17:46 ` [PATCH] crypto: arm64/gcm - remove Wunused-const-variable ghash_cpu_feature Eric Biggers
2021-05-28 13:51 ` Austin Kim
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=20210527062809.GA1251@raspberrypi \
--to=austindh.kim@gmail$(echo .)com \
--cc=austin.kim@lge$(echo .)com \
--cc=catalin.marinas@arm$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=herbert@gondor$(echo .)apana.org.au \
--cc=jmorris@namei$(echo .)org \
--cc=john.johansen@canonical$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-crypto@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-security-module@vger$(echo .)kernel.org \
--cc=serge@hallyn$(echo .)com \
--cc=will@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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