From: Robert Elliott <elliott@hpe.com>
To: herbert@gondor.apana.org.au, davem@davemloft.net, corbet@lwn.net,
linux-crypto@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Robert Elliott <elliott@hpe.com>
Subject: [PATCH v2 5/8] crypto: x86/sm3 - add kernel-doc comments to assembly
Date: Mon, 19 Dec 2022 12:55:52 -0600 [thread overview]
Message-ID: <20221219185555.433233-6-elliott@hpe.com> (raw)
In-Reply-To: <20221219185555.433233-1-elliott@hpe.com>
Add kernel-doc comments for assembly language functions exported to
C glue code.
Signed-off-by: Robert Elliott <elliott@hpe.com>
---
arch/x86/crypto/sm3-avx-asm_64.S | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/arch/x86/crypto/sm3-avx-asm_64.S b/arch/x86/crypto/sm3-avx-asm_64.S
index 503bab450a91..30e51c681c07 100644
--- a/arch/x86/crypto/sm3-avx-asm_64.S
+++ b/arch/x86/crypto/sm3-avx-asm_64.S
@@ -322,18 +322,18 @@
.text
-/*
- * Transform nblocks*64 bytes (nblocks*16 32-bit words) at DATA.
+/**
+ * sm3_transform_avx - Calculate SM3 hash using x86 AVX feature set
+ * @state: address of 32-byte context (%rdi, RSTATE macro)
+ * @data: address of data (%rsi, RDATA macro);
+ * must be at least 64 bytes and a multiple of 64 bytes
+ * @nblocks: number of 64-byte blocks (%rdx, RNBLKS macro);
+ * must be >= 1
*
- * void sm3_transform_avx(struct sm3_state *state,
- * const u8 *data, int nblocks);
+ * Return: none. However, the @state buffer is updated.
+ * Prototype: asmlinkage void sm3_transform_avx(u32 *state, const u8 *data, int nblocks);
*/
SYM_TYPED_FUNC_START(sm3_transform_avx)
- /* input:
- * %rdi: ctx, CTX
- * %rsi: data (64*nblks bytes)
- * %rdx: nblocks
- */
vzeroupper;
pushq %rbp;
--
2.38.1
next prev parent reply other threads:[~2022-12-19 18:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 6:38 [PATCH 0/8] crypto: kernel-doc for assembly language Robert Elliott
2022-12-15 6:38 ` [PATCH 1/8] crypto: clean up kernel-doc headers Robert Elliott
2022-12-15 6:38 ` [PATCH 2/8] doc: support kernel-doc for asm functions Robert Elliott
2022-12-15 6:38 ` [PATCH 3/8] crypto: x86/sha - add kernel-doc comments to assembly Robert Elliott
2022-12-15 6:38 ` [PATCH 4/8] crypto: x86/crc " Robert Elliott
2022-12-15 6:38 ` [PATCH 5/8] crypto: x86/sm3 " Robert Elliott
2022-12-15 6:38 ` [PATCH 6/8] crypto: x86/ghash " Robert Elliott
2022-12-15 6:38 ` [PATCH 7/8] crypto: x86/blake2s " Robert Elliott
2022-12-15 6:38 ` [PATCH 8/8] crypto: x86/chacha " Robert Elliott
2022-12-19 18:55 ` [PATCH v2 0/8] crypto: kernel-doc for assembly language Robert Elliott
2022-12-19 18:55 ` [PATCH v2 1/8] crypto: clean up kernel-doc headers Robert Elliott
2022-12-19 18:55 ` [PATCH v2 2/8] doc: support kernel-doc for asm functions Robert Elliott
2022-12-19 18:55 ` [PATCH v2 3/8] crypto: x86/sha - add kernel-doc comments to assembly Robert Elliott
2022-12-19 18:55 ` [PATCH v2 4/8] crypto: x86/crc " Robert Elliott
2022-12-19 18:55 ` Robert Elliott [this message]
2022-12-19 18:55 ` [PATCH v2 6/8] crypto: x86/ghash " Robert Elliott
2022-12-20 6:01 ` Eric Biggers
2022-12-19 18:55 ` [PATCH v2 7/8] crypto: x86/blake2s " Robert Elliott
2022-12-19 18:55 ` [PATCH v2 8/8] crypto: x86/chacha " Robert Elliott
2022-12-20 6:05 ` 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=20221219185555.433233-6-elliott@hpe.com \
--to=elliott@hpe.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@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