From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, "Jason A . Donenfeld " <Jason@zx2c4.com>
Subject: [PATCH v3 3/3] crypto: lib - remove __HAVE_ARCH_CRYPTO_MEMNEQ
Date: Mon, 25 Jul 2022 11:36:36 -0700 [thread overview]
Message-ID: <20220725183636.97326-4-ebiggers@kernel.org> (raw)
In-Reply-To: <20220725183636.97326-1-ebiggers@kernel.org>
From: Eric Biggers <ebiggers@google.com>
No architecture actually defines this, so it's unneeded.
Signed-off-by: Eric Biggers <ebiggers@google.com>
---
lib/crypto/memneq.c | 4 ----
1 file changed, 4 deletions(-)
diff --git a/lib/crypto/memneq.c b/lib/crypto/memneq.c
index d1e8c86fbb0fcf..243d8677cc515d 100644
--- a/lib/crypto/memneq.c
+++ b/lib/crypto/memneq.c
@@ -63,8 +63,6 @@
#include <crypto/algapi.h>
#include <linux/module.h>
-#ifndef __HAVE_ARCH_CRYPTO_MEMNEQ
-
/* Generic path for arbitrary size */
static inline unsigned long
__crypto_memneq_generic(const void *a, const void *b, size_t size)
@@ -173,5 +171,3 @@ noinline unsigned long __crypto_memneq(const void *a, const void *b,
}
}
EXPORT_SYMBOL(__crypto_memneq);
-
-#endif /* __HAVE_ARCH_CRYPTO_MEMNEQ */
--
2.37.0
next prev parent reply other threads:[~2022-07-25 18:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 18:36 [PATCH v3 0/3] crypto: lib - create utils module Eric Biggers
2022-07-25 18:36 ` [PATCH v3 1/3] crypto: lib - create utils module and move __crypto_memneq into it Eric Biggers
2022-07-25 22:10 ` Jason A. Donenfeld
2022-07-25 18:36 ` [PATCH v3 2/3] crypto: lib - move __crypto_xor into utils Eric Biggers
2022-07-25 22:09 ` Jason A. Donenfeld
2022-07-26 1:00 ` Eric Biggers
2022-07-26 13:46 ` Ard Biesheuvel
2022-08-26 4:44 ` Eric Biggers
2022-08-26 4:46 ` Herbert Xu
2022-08-26 4:48 ` Eric Biggers
2022-08-26 4:52 ` Herbert Xu
2022-08-26 5:07 ` Eric Biggers
2022-07-25 18:36 ` Eric Biggers [this message]
2022-07-25 22:07 ` [PATCH v3 3/3] crypto: lib - remove __HAVE_ARCH_CRYPTO_MEMNEQ Jason A. Donenfeld
2022-07-26 0:51 ` Eric Biggers
2022-08-19 10:59 ` [PATCH v3 0/3] crypto: lib - create utils module 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=20220725183636.97326-4-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).