From: Thomas Huth <thuth@redhat.com>
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>
Subject: Re: [PATCH] lib/crypto: docs: Improve introduction sentence
Date: Thu, 9 Jul 2026 08:19:41 +0200 [thread overview]
Message-ID: <aa109637-0102-4341-8bb3-02bf2a90a170@redhat.com> (raw)
In-Reply-To: <20260709022747.44635-1-ebiggers@kernel.org>
On 09/07/2026 04.27, Eric Biggers wrote:
> Make it clear that lib/crypto/ is a kernel-internal library. It's easy
> for people to come across this page, especially the HTML version online,
> without that context.
>
> Signed-off-by: Eric Biggers <ebiggers@kernel.org>
> ---
> Documentation/crypto/libcrypto.rst | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/crypto/libcrypto.rst b/Documentation/crypto/libcrypto.rst
> index a1557d45b0e5..0733e603d229 100644
> --- a/Documentation/crypto/libcrypto.rst
> +++ b/Documentation/crypto/libcrypto.rst
> @@ -4,8 +4,9 @@
> Crypto library
> ==============
>
> -``lib/crypto/`` provides faster and easier access to cryptographic algorithms
> -than the traditional crypto API.
> +The Linux kernel's crypto library (``lib/crypto/``) provides kernel-internal
> +users of cryptographic algorithms with faster and easier access to those
> +algorithms than the traditional kernel crypto API.
Reviewed-by: Thomas Huth <thuth@redhat.com>
prev parent reply other threads:[~2026-07-09 6:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 2:27 [PATCH] lib/crypto: docs: Improve introduction sentence Eric Biggers
2026-07-09 6:19 ` Thomas Huth [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=aa109637-0102-4341-8bb3-02bf2a90a170@redhat.com \
--to=thuth@redhat.com \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@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