From: Randy Dunlap <rdunlap@infradead.org>
To: Eric Biggers <ebiggers@kernel.org>, linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Subject: Re: [PATCH v2 2/2] lib/crypto: docs: Add rst documentation to Documentation/crypto/
Date: Sat, 18 Apr 2026 16:52:25 -0700 [thread overview]
Message-ID: <5f476f04-b6ea-4c56-b416-da4c5cec19a0@infradead.org> (raw)
In-Reply-To: <20260418192138.15556-3-ebiggers@kernel.org>
On 4/18/26 12:21 PM, Eric Biggers wrote:
> Add a documentation file Documentation/crypto/libcrypto.rst which
> provides a high-level overview of lib/crypto/.
>
> Also add several sub-pages which include the kernel-doc for the
> algorithms that have it. This makes the existing, quite extensive
> kernel-doc start being included in the HTML and PDF documentation.
>
> Note that the intent is very much *not* that everyone has to read these
> Documentation/ files. The library is intended to be straightforward and
> use familiar conventions; generally it should be possible to dive right
> into the kernel-doc. You shouldn't need to read a lot of documentation
> to just call `sha256()`, for example, or to run the unit tests if you're
> already familiar with KUnit. (This differs from the traditional crypto
> API which has a larger barrier to entry.)
>
> Nevertheless, this seems worth adding. Hopefully it is useful and makes
> LWN no longer consider the library to be "meticulously undocumented".
>
> Reviewed-by: Ard Biesheuvel <ardb@kernel.org>
> Signed-off-by: Eric Biggers <ebiggers@kernel.org>
Tested-by: Randy Dunlap <rdunlap@infradead.org>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> Documentation/crypto/index.rst | 2 +-
> .../crypto/libcrypto-blockcipher.rst | 19 ++
> Documentation/crypto/libcrypto-hash.rst | 86 +++++++++
> Documentation/crypto/libcrypto-signature.rst | 11 ++
> Documentation/crypto/libcrypto-utils.rst | 6 +
> Documentation/crypto/libcrypto.rst | 165 ++++++++++++++++++
> Documentation/crypto/sha3.rst | 2 +
> 7 files changed, 290 insertions(+), 1 deletion(-)
> create mode 100644 Documentation/crypto/libcrypto-blockcipher.rst
> create mode 100644 Documentation/crypto/libcrypto-hash.rst
> create mode 100644 Documentation/crypto/libcrypto-signature.rst
> create mode 100644 Documentation/crypto/libcrypto-utils.rst
> create mode 100644 Documentation/crypto/libcrypto.rst
>
--
~Randy
prev parent reply other threads:[~2026-04-18 23:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-18 19:21 [PATCH v2 0/2] Improve the crypto library documentation Eric Biggers
2026-04-18 19:21 ` [PATCH v2 1/2] docs: kdoc: Expand 'at_least' when creating parameter list Eric Biggers
2026-04-18 23:50 ` Randy Dunlap
2026-04-18 19:21 ` [PATCH v2 2/2] lib/crypto: docs: Add rst documentation to Documentation/crypto/ Eric Biggers
2026-04-18 23:52 ` Randy Dunlap [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=5f476f04-b6ea-4c56-b416-da4c5cec19a0@infradead.org \
--to=rdunlap@infradead.org \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=corbet@lwn.net \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@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