From: Arnd Bergmann <arnd@kernel.org>
To: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>
Cc: Arnd Bergmann <arnd@arndb.de>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Lukas Wunner <lukas@wunner.de>,
Eric Biggers <ebiggers@google.com>,
Ard Biesheuvel <ardb@kernel.org>,
Stefan Berger <stefanb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Keith Busch <kbusch@kernel.org>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] crypto: testmgr - drop unused static const arrays
Date: Wed, 5 Feb 2025 13:13:15 +0100 [thread overview]
Message-ID: <20250205121342.344475-1-arnd@kernel.org> (raw)
From: Arnd Bergmann <arnd@arndb.de>
The ones[] and zeroes[] definitions were previously used by the
rocksoft tests that are now gone. With extra warnings enabled,
gcc now complains about these:
crypto/testmgr.h:6021:17: error: 'ones' defined but not used [-Werror=unused-const-variable=]
6021 | static const u8 ones[4096] = { [0 ... 4095] = 0xff };
| ^~~~
crypto/testmgr.h:6020:17: error: 'zeroes' defined but not used [-Werror=unused-const-variable=]
6020 | static const u8 zeroes[4096] = { [0 ... 4095] = 0 };
| ^~~~~~
Drop them as well.
Fixes: dad9cb81bc30 ("crypto: crc64-rocksoft - remove from crypto API")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
---
crypto/testmgr.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/crypto/testmgr.h b/crypto/testmgr.h
index 4ab05046b734..61c7ae731052 100644
--- a/crypto/testmgr.h
+++ b/crypto/testmgr.h
@@ -6017,9 +6017,6 @@ static const struct hash_testvec rmd160_tv_template[] = {
}
};
-static const u8 zeroes[4096] = { [0 ... 4095] = 0 };
-static const u8 ones[4096] = { [0 ... 4095] = 0xff };
-
static const struct hash_testvec crct10dif_tv_template[] = {
{
.plaintext = "abc",
--
2.39.5
next reply other threads:[~2025-02-05 12:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 12:13 Arnd Bergmann [this message]
2025-02-05 15:34 ` [PATCH] crypto: testmgr - drop unused static const arrays Eric Biggers
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=20250205121342.344475-1-arnd@kernel.org \
--to=arnd@kernel.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=ebiggers@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=kbusch@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=martin.petersen@oracle.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=stefanb@linux.ibm.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