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 v2 0/3] crypto: lib - create utils module
Date: Fri, 15 Jul 2022 23:29:17 -0700 [thread overview]
Message-ID: <20220716062920.210381-1-ebiggers@kernel.org> (raw)
Create a utils module in lib/crypto/, and move __crypto_memneq,
__crypto_xor, and crypto_simd_disabled_for_test into it.
This supersedes "crypto: xor - move __crypto_xor into lib/"
(https://lore.kernel.org/linux-crypto/20220709215453.262237-1-ebiggers@kernel.org/T/#u).
Eric Biggers (3):
crypto: lib - create utils module and move __crypto_memneq into it
crypto: lib - move __crypto_xor into utils
crypto: lib - move crypto_simd_disabled_for_test into utils
crypto/Kconfig | 2 +-
crypto/algapi.c | 77 ---------------------------------
lib/Kconfig | 3 --
lib/Makefile | 1 -
lib/crypto/Kconfig | 8 ++--
lib/crypto/Makefile | 3 ++
lib/{ => crypto}/memneq.c | 0
lib/crypto/utils.c | 91 +++++++++++++++++++++++++++++++++++++++
8 files changed, 100 insertions(+), 85 deletions(-)
rename lib/{ => crypto}/memneq.c (100%)
create mode 100644 lib/crypto/utils.c
base-commit: ec8f7f4821d5e70d71601519bc2325b311324a96
--
2.37.0
next reply other threads:[~2022-07-16 6:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 6:29 Eric Biggers [this message]
2022-07-16 6:29 ` [PATCH v2 1/3] crypto: lib - create utils module and move __crypto_memneq into it Eric Biggers
2022-07-16 6:29 ` [PATCH v2 2/3] crypto: lib - move __crypto_xor into utils Eric Biggers
2022-07-16 6:29 ` [PATCH v2 3/3] crypto: lib - move crypto_simd_disabled_for_test " Eric Biggers
2022-07-16 18:32 ` Jason A. Donenfeld
2022-07-19 4:34 ` Eric Biggers
2022-07-21 7:01 ` Eric Biggers
2022-07-21 7:36 ` 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=20220716062920.210381-1-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