From: "Ard Biesheuvel" <ardb@kernel.org>
To: "Eric Biggers" <ebiggers@kernel.org>, linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.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>,
"Randy Dunlap" <rdunlap@infradead.org>
Subject: Re: [PATCH 0/2] Improve the crypto library documentation
Date: Fri, 17 Apr 2026 15:47:32 +0200 [thread overview]
Message-ID: <3bda17f4-c9b0-46f1-a3bf-50337b2e91e2@app.fastmail.com> (raw)
In-Reply-To: <20260417065529.64925-1-ebiggers@kernel.org>
On Fri, 17 Apr 2026, at 08:55, Eric Biggers wrote:
> While the crypto library already has a lot of kerneldoc, it's not being
> included in the HTML or PDF documentation. Update Documentation/crypto/
> to include it, and also add a high-level overview of the library.
>
> I'd like to take this series via the libcrypto tree for 7.1.
>
> Eric Biggers (2):
> docs: kdoc: Expand 'at_least' when creating parameter list
> lib/crypto: docs: Add rst documentation to Documentation/crypto/
>
Reviewed-by: Ard Biesheuvel <ardb@kernel.org>
I think this hits the spot wrt scope and level of detail.
prev parent reply other threads:[~2026-04-17 13:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 6:55 [PATCH 0/2] Improve the crypto library documentation Eric Biggers
2026-04-17 6:55 ` [PATCH 1/2] docs: kdoc: Expand 'at_least' when creating parameter list Eric Biggers
2026-04-17 7:18 ` Jonathan Corbet
2026-04-17 6:55 ` [PATCH 2/2] lib/crypto: docs: Add rst documentation to Documentation/crypto/ Eric Biggers
2026-04-17 7:22 ` [PATCH 0/2] Improve the crypto library documentation Jonathan Corbet
2026-04-17 13:47 ` Ard Biesheuvel [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=3bda17f4-c9b0-46f1-a3bf-50337b2e91e2@app.fastmail.com \
--to=ardb@kernel.org \
--cc=Jason@zx2c4.com \
--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 \
--cc=rdunlap@infradead.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