From: Randy Dunlap <rdunlap@infradead.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Crypto <linux-crypto@vger.kernel.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] crypto: Add explicit title heading to API docs
Date: Sat, 20 Sep 2025 12:01:46 -0700 [thread overview]
Message-ID: <72f5bbdf-2054-42a9-a9bd-aec3ebefc71e@infradead.org> (raw)
In-Reply-To: <20250920001650.10474-2-bagasdotme@gmail.com>
On 9/19/25 5:16 PM, Bagas Sanjaya wrote:
> Documentation for crypto programming interfaces lack explicit title.
> As such, all its sections become entries in the toctree index.
>
> Add the title heading to tidy up toctree.
Yes, much neater. Thanks.
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Randy Dunlap <rdunlap@infradead.org>
>
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
> Documentation/crypto/api-aead.rst | 3 +++
> Documentation/crypto/api-akcipher.rst | 3 +++
> Documentation/crypto/api-digest.rst | 3 +++
> Documentation/crypto/api-kpp.rst | 3 +++
> Documentation/crypto/api-rng.rst | 3 +++
> Documentation/crypto/api-sig.rst | 3 +++
> Documentation/crypto/api-skcipher.rst | 3 +++
> 7 files changed, 21 insertions(+)
>
> diff --git a/Documentation/crypto/api-aead.rst b/Documentation/crypto/api-aead.rst
> index d15256f1ae3696..78d073319f96a3 100644
> --- a/Documentation/crypto/api-aead.rst
> +++ b/Documentation/crypto/api-aead.rst
> @@ -1,3 +1,6 @@
> +Authenticated Encryption With Associated Data (AEAD)
> +====================================================
> +
> Authenticated Encryption With Associated Data (AEAD) Algorithm Definitions
> --------------------------------------------------------------------------
>
> diff --git a/Documentation/crypto/api-akcipher.rst b/Documentation/crypto/api-akcipher.rst
> index ca1ecdd4a7d378..a31f5aef76678f 100644
> --- a/Documentation/crypto/api-akcipher.rst
> +++ b/Documentation/crypto/api-akcipher.rst
> @@ -1,3 +1,6 @@
> +Asymmetric Cipher
> +=================
> +
> Asymmetric Cipher Algorithm Definitions
> ---------------------------------------
>
> diff --git a/Documentation/crypto/api-digest.rst b/Documentation/crypto/api-digest.rst
> index 7a1e670d6ce1a4..02a2bcc26a6470 100644
> --- a/Documentation/crypto/api-digest.rst
> +++ b/Documentation/crypto/api-digest.rst
> @@ -1,3 +1,6 @@
> +Message Digest
> +==============
> +
> Message Digest Algorithm Definitions
> ------------------------------------
>
> diff --git a/Documentation/crypto/api-kpp.rst b/Documentation/crypto/api-kpp.rst
> index 7d86ab906bdf79..5794e2d10c9562 100644
> --- a/Documentation/crypto/api-kpp.rst
> +++ b/Documentation/crypto/api-kpp.rst
> @@ -1,3 +1,6 @@
> +Key-agreement Protocol Primitives (KPP)
> +=======================================
> +
> Key-agreement Protocol Primitives (KPP) Cipher Algorithm Definitions
> --------------------------------------------------------------------
>
> diff --git a/Documentation/crypto/api-rng.rst b/Documentation/crypto/api-rng.rst
> index 10ba7436cee48e..23a94c0b272eef 100644
> --- a/Documentation/crypto/api-rng.rst
> +++ b/Documentation/crypto/api-rng.rst
> @@ -1,3 +1,6 @@
> +Random Number Generator (RNG)
> +=============================
> +
> Random Number Algorithm Definitions
> -----------------------------------
>
> diff --git a/Documentation/crypto/api-sig.rst b/Documentation/crypto/api-sig.rst
> index aaec18e26d545f..4d8aba8aee8e04 100644
> --- a/Documentation/crypto/api-sig.rst
> +++ b/Documentation/crypto/api-sig.rst
> @@ -1,3 +1,6 @@
> +Asymmetric Signature
> +====================
> +
> Asymmetric Signature Algorithm Definitions
> ------------------------------------------
>
> diff --git a/Documentation/crypto/api-skcipher.rst b/Documentation/crypto/api-skcipher.rst
> index 04d6cc5357c810..4b7c8160790a3c 100644
> --- a/Documentation/crypto/api-skcipher.rst
> +++ b/Documentation/crypto/api-skcipher.rst
> @@ -1,3 +1,6 @@
> +Symmetric Key Cipher
> +====================
> +
> Block Cipher Algorithm Definitions
> ----------------------------------
>
>
> base-commit: 381e8ee368234a51b3a4f231f6f24ff0b09d9f9e
--
~Randy
next prev parent reply other threads:[~2025-09-20 19:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-20 0:16 Bagas Sanjaya
2025-09-20 19:01 ` Randy Dunlap [this message]
2025-09-28 3:59 ` 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=72f5bbdf-2054-42a9-a9bd-aec3ebefc71e@infradead.org \
--to=rdunlap@infradead.org \
--cc=bagasdotme@gmail.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
all inboxes | Powered by JetHome®