From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org
Subject: [PATCH 0/5] crypto: arm64 - clean up backwards function names
Date: Mon, 9 Oct 2023 23:41:22 -0700 [thread overview]
Message-ID: <20231010064127.323261-1-ebiggers@kernel.org> (raw)
In the Linux kernel, a function whose name has two leading underscores
is conventionally called by the same-named function without leading
underscores -- not the other way around. Some of the arm64 crypto code
got this backwards. Fix it.
Eric Biggers (5):
crypto: arm64/sha1-ce - clean up backwards function names
crypto: arm64/sha2-ce - clean up backwards function names
crypto: arm64/sha512-ce - clean up backwards function names
crypto: arm64/sha256 - clean up backwards function names
crypto: arm64/sha512 - clean up backwards function names
arch/arm64/crypto/sha1-ce-core.S | 8 ++++----
arch/arm64/crypto/sha1-ce-glue.c | 21 ++++++++++----------
arch/arm64/crypto/sha2-ce-core.S | 8 ++++----
arch/arm64/crypto/sha2-ce-glue.c | 31 +++++++++++++++---------------
arch/arm64/crypto/sha256-glue.c | 26 ++++++++++++-------------
arch/arm64/crypto/sha512-ce-core.S | 8 ++++----
arch/arm64/crypto/sha512-ce-glue.c | 26 ++++++++++++-------------
arch/arm64/crypto/sha512-glue.c | 12 +++++-------
8 files changed, 69 insertions(+), 71 deletions(-)
base-commit: 8468516f9f93a41dc65158b6428a1a1039c68f20
--
2.42.0
next reply other threads:[~2023-10-10 6:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 6:41 Eric Biggers [this message]
2023-10-10 6:41 ` [PATCH 1/5] crypto: arm64/sha1-ce - clean up backwards function names Eric Biggers
2023-10-10 6:41 ` [PATCH 2/5] crypto: arm64/sha2-ce " Eric Biggers
2023-10-10 6:41 ` [PATCH 3/5] crypto: arm64/sha512-ce " Eric Biggers
2023-10-10 6:41 ` [PATCH 4/5] crypto: arm64/sha256 " Eric Biggers
2023-10-10 6:41 ` [PATCH 5/5] crypto: arm64/sha512 " Eric Biggers
2023-10-20 5:53 ` [PATCH 0/5] crypto: arm64 " 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=20231010064127.323261-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=linux-crypto@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).