public inbox for linux-crypto@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	Ard Biesheuvel <ardb@kernel.org>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Ignat Korchagin <ignat@linux.win>,
	Jarkko Sakkinen <jarkko@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>, Lukas Wunner <lukas@wunner.de>,
	Randy Dunlap <rdunlap@infradead.org>,
	Yiming Qian <yimingqian591@gmail.com>
Subject: [GIT PULL] Crypto library fix and documentation update for 7.1
Date: Tue, 21 Apr 2026 11:38:47 -0700	[thread overview]
Message-ID: <20260421183847.GA2202@quark> (raw)

The following changes since commit d60bc140158342716e13ff0f8aa65642f43ba053:

  Merge tag 'pwrseq-updates-for-v7.1-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux (2026-04-13 20:28:22 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git tags/libcrypto-for-linus

for you to fetch changes up to e9af4f47d4a036b4be67e4be361f62e05081f7bf:

  lib/crypto: docs: Add rst documentation to Documentation/crypto/ (2026-04-18 17:32:02 -0700)

----------------------------------------------------------------

- Fix an integer underflow in the mpi library

- Improve the crypto library documentation

----------------------------------------------------------------
Eric Biggers (2):
      docs: kdoc: Expand 'at_least' when creating parameter list
      lib/crypto: docs: Add rst documentation to Documentation/crypto/

Lukas Wunner (1):
      lib/crypto: mpi: Fix integer underflow in mpi_read_raw_from_sgl()

 Documentation/crypto/index.rst                 |   2 +-
 Documentation/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 +
 lib/crypto/mpi/mpicoder.c                      |   2 +-
 tools/lib/python/kdoc/kdoc_parser.py           |   5 +
 9 files changed, 296 insertions(+), 2 deletions(-)
 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

             reply	other threads:[~2026-04-21 18:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21 18:38 Eric Biggers [this message]
2026-04-21 18:50 ` [GIT PULL] Crypto library fix and documentation update for 7.1 pr-tracker-bot

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=20260421183847.GA2202@quark \
    --to=ebiggers@kernel.org \
    --cc=Jason@zx2c4.com \
    --cc=ardb@kernel.org \
    --cc=corbet@lwn.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=ignat@linux.win \
    --cc=jarkko@kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=rdunlap@infradead.org \
    --cc=torvalds@linux-foundation.org \
    --cc=yimingqian591@gmail.com \
    /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