From: Herbert Xu <herbert@gondor.apana.org.au>
To: Linus Torvalds <torvalds@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: [GIT PULL] Crypto Fixes for 6.17
Date: Fri, 8 Aug 2025 13:41:51 +0800 [thread overview]
Message-ID: <aJWOH9GgXhoJsHp6@gondor.apana.org.au> (raw)
Hi Linus:
The following changes since commit bf24d64268544379d9a9b5b8efc2bb03967703b3:
crypto: keembay - Use min() to simplify ocs_create_linked_list_from_sg() (2025-07-27 22:41:45 +1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git tags/v6.17-p2
for you to fetch changes up to 9d9b193ed73a65ec47cf1fd39925b09da8216461:
crypto: hash - Increase HASH_MAX_DESCSIZE for hmac(sha3-224-s390) (2025-08-01 19:40:54 +0800)
----------------------------------------------------------------
This push fixes a regression that breaks hmac(sha3-224-s390).
----------------------------------------------------------------
Herbert Xu (1):
crypto: hash - Increase HASH_MAX_DESCSIZE for hmac(sha3-224-s390)
include/crypto/hash.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Thanks,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next reply other threads:[~2025-08-08 5:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 5:41 Herbert Xu [this message]
2025-08-09 4:32 ` Linus Torvalds
2025-08-09 18:22 ` Vegard Nossum
2025-08-10 4:51 ` Linus Torvalds
2025-08-11 4:44 ` [PATCH] crypto: hash - Make HASH_MAX_DESCSIZE a bit more obvious Herbert Xu
2025-08-11 7:10 ` Linus Torvalds
2025-08-11 16:57 ` Eric Biggers
2025-08-09 5:19 ` [GIT PULL] Crypto Fixes for 6.17 pr-tracker-bot
2025-09-19 4:10 Herbert Xu
2025-09-19 17:15 ` pr-tracker-bot
2025-09-24 19:06 ` Eric Biggers
2025-11-11 7:57 ` Gu Bowen
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=aJWOH9GgXhoJsHp6@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=davem@davemloft.net \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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®