From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Herbert Xu <herbert@gondor.apana.org.au>,
Linux Crypto List <linux-crypto@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Signed-off-by missing for commit in the crypto tree
Date: Mon, 5 May 2025 19:55:27 +1000 [thread overview]
Message-ID: <20250505195527.4c4237c4@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 2290 bytes --]
Hi all,
Commits
e4274cd4f727 ("crypto: hisilicon/qm - replace devm_kzalloc with devm_kcalloc")
3f9ea3a5618e ("crypto: hisilicon/qm - remove sizeof(char)")
7da3b0ff2af8 ("crypto: sun8i-ce-hash - use pm_runtime_resume_and_get()")
2c870574fb94 ("crypto: sun8i-ce - undo runtime PM changes during driver removal")
24418b58792a ("hwrng: rockchip - add support for RK3576's RNG")
e511999438e1 ("dt-bindings: rng: rockchip,rk3588-rng: add rk3576-rng compatible")
13917ce458c7 ("crypto: rng - fix documentation for crypto_rng_alg()")
c6527b8ca148 ("crypto: qat - add qat_6xxx driver")
bed3233d9e4f ("crypto: qat - add firmware headers for GEN6 devices")
4903f74450d1 ("crypto: qat - update firmware api")
e9833be85348 ("crypto: qat - export adf_init_admin_pm()")
a260a62349b0 ("crypto: qat - expose configuration functions")
8e84a854176a ("crypto: qat - export adf_get_service_mask()")
ff193f6c14e9 ("crypto: qat - add GEN6 firmware loader")
c1e216382091 ("crypto: qat - refactor FW signing algorithm")
25177bb3f705 ("crypto: qat - use pr_fmt() in qat uclo.c")
5fc9923d1554 ("crypto: qat - refactor compression template logic")
424b3c3cfbae ("crypto: qat - rename and relocate timer logic")
9b6fc5b6e9c0 ("crypto: qat - include qat_common in top Makefile")
f230dcfe428b ("crypto: lib/sha256 - improve function prototypes")
e42b6c1e17cc ("crypto: sha256 - remove sha256_base.h")
91c5c4bf145d ("crypto: x86/sha256 - implement library instead of shash")
42802c7f8eff ("crypto: sparc/sha256 - implement library instead of shash")
1a92dd688525 ("crypto: sparc - move opcodes.h into asm directory")
d31058b2589f ("crypto: s390/sha256 - implement library instead of shash")
fe11c8974fdc ("crypto: riscv/sha256 - implement library instead of shash")
9d2b1924c137 ("crypto: powerpc/sha256 - implement library instead of shash")
19c9460ea05b ("crypto: mips/sha256 - implement library instead of shash")
6df537365d25 ("crypto: arm64/sha256 - implement library instead of shash")
4fcab0fbfd54 ("crypto: arm64/sha256 - remove obsolete chunking logic")
7f4bd270972c ("crypto: arm/sha256 - implement library instead of shash")
are missing a Signed-off-by from their committer.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-05-05 9:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 9:55 Stephen Rothwell [this message]
2025-05-05 10:22 ` linux-next: Signed-off-by missing for commit in the crypto tree Herbert Xu
-- strict thread matches above, loose matches on Subject: below --
2025-05-20 12:45 Stephen Rothwell
2024-10-27 21:15 Stephen Rothwell
2023-07-16 21:55 Stephen Rothwell
2023-07-17 13:00 ` Mahmoud Adam
2023-03-13 21:42 Stephen Rothwell
2020-11-13 7:22 Stephen Rothwell
2020-01-09 9:00 Stephen Rothwell
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=20250505195527.4c4237c4@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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