public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Robert Elliott <elliott@hpe.com>
Cc: 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
Subject: Re: [PATCH v2 8/8] crypto: x86/chacha - add kernel-doc comments to assembly
Date: Mon, 19 Dec 2022 22:05:40 -0800	[thread overview]
Message-ID: <Y6FQtNgZy8lXKfiz@sol.localdomain> (raw)
In-Reply-To: <20221219185555.433233-9-elliott@hpe.com>

On Mon, Dec 19, 2022 at 12:55:55PM -0600, Robert Elliott wrote:
> +/**
> + * chacha_2block_xor_avx2 - Encrypt 2 blocks using the x86 AVX2 feature set
> + * @state:	address of input state matrix, s (%rdi)
> + * @dst:	address of up to 2 data blocks output, o (%rsi)
> + * @src:	address of up to 2 data blocks input, i (%rdx)
> + * @len:	input/output length in bytes (%rcx)
> + * @nrounds:	number of rounds (%r8d)
> + *
> + * This function encrypts two ChaCha blocks by loading the state
> + * matrix twice across four AVX registers. It performs matrix operations
> + * on four words in each matrix in parallel, but requires shuffling to
> + * rearrange the words after each round.

2 blocks, or up to 2 blocks?  What does that mean?

> + *
> + * Return:	none
> + * Prototype:	asmlinkage void chacha_2block_xor_avx2(u32 *state, u8 *dst, const u8 *src,
> + *						       unsigned int len, int nrounds);

When the return type is void, there is no need to write "Return: none".

- Eric

      reply	other threads:[~2022-12-20  6:05 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   ` [PATCH v2 5/8] crypto: x86/sm3 " Robert Elliott
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 [this message]

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=Y6FQtNgZy8lXKfiz@sol.localdomain \
    --to=ebiggers@kernel.org \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=elliott@hpe.com \
    --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