From: Eric Biggers <ebiggers@kernel.org>
To: 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>,
kunit-dev@googlegroups.com,
Brendan Higgins Brendan Higgins
<brendan.higgins@linux.devbrendan.higgins@linux.dev>,
David Gow <david@davidgow.net>,
Rae Moar <raemoar63@gmail.comRaeMoarraemoar63@gmail.com>,
Eric Biggers <ebiggers@kernel.org>
Subject: [PATCH 0/2] Make 'kunit.py run --alltests' run all crypto library tests
Date: Fri, 13 Mar 2026 20:59:25 -0700 [thread overview]
Message-ID: <20260314035927.51351-1-ebiggers@kernel.org> (raw)
This series makes the KUnit all_tests.config enable all the crypto
library options that have KUnit tests, so that all these tests will be
run in testing systems use 'kunit.py run --alltests'. (For example,
KernelCI is planned to start doing that [1].) To do this easily in both
that file and in lib/crypto/.kunitconfig, introduce a kconfig option
CRYPTO_LIB_ENABLE_ALL_FOR_KUNIT for this purpose.
This series is targeting libcrypto-next.
[1] https://lore.kernel.org/kernelci/4fd302e0-ffa7-4bbf-a94a-c8879fde32f4@sirena.org.uk
Eric Biggers (2):
lib/crypto: tests: Introduce CRYPTO_LIB_ENABLE_ALL_FOR_KUNIT
kunit: configs: Enable all crypto library tests in all_tests.config
lib/crypto/.kunitconfig | 22 +-----------------
lib/crypto/tests/Kconfig | 24 ++++++++++++++++++++
tools/testing/kunit/configs/all_tests.config | 2 ++
3 files changed, 27 insertions(+), 21 deletions(-)
base-commit: ce260754bb435aea18e6a1a1ce3759249013f5a4
--
2.53.0
next reply other threads:[~2026-03-14 4:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-14 3:59 Eric Biggers [this message]
2026-03-14 3:59 ` [PATCH 1/2] lib/crypto: tests: Introduce CRYPTO_LIB_ENABLE_ALL_FOR_KUNIT Eric Biggers
2026-03-14 3:59 ` [PATCH 2/2] kunit: configs: Enable all crypto library tests in all_tests.config Eric Biggers
2026-03-17 16:38 ` [PATCH 0/2] Make 'kunit.py run --alltests' run all crypto library tests Eric Biggers
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=20260314035927.51351-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=brendan.higgins@linux.devbrendan.higgins \
--cc=herbert@gondor.apana.org.au \
--cc=kunit-dev@googlegroups.com \
--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