From: Eric Biggers <ebiggers@kernel.org>
To: stable@vger.kernel.org
Cc: linux-crypto@vger.kernel.org, kunit-dev@googlegroups.com,
Eric Biggers <ebiggers@kernel.org>,
Ard Biesheuvel <ardb@kernel.org>
Subject: [PATCH 6.18 4/8] kunit: configs: Enable all CRC tests in all_tests.config
Date: Tue, 21 Apr 2026 14:05:50 -0700 [thread overview]
Message-ID: <20260421210554.36096-5-ebiggers@kernel.org> (raw)
In-Reply-To: <20260421210554.36096-1-ebiggers@kernel.org>
commit 44ff3791d6295f7b51dd2711aad6a03dd79aef22 upstream.
The new option CONFIG_CRC_ENABLE_ALL_FOR_KUNIT enables all the CRC code
that has KUnit tests, causing CONFIG_KUNIT_ALL_TESTS to enable all these
tests. Add this option to all_tests.config so that kunit.py will run
them when passed the --alltests option.
Acked-by: Ard Biesheuvel <ardb@kernel.org>
Link: https://lore.kernel.org/r/20260314172224.15152-1-ebiggers@kernel.org
Signed-off-by: Eric Biggers <ebiggers@kernel.org>
---
tools/testing/kunit/configs/all_tests.config | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/testing/kunit/configs/all_tests.config b/tools/testing/kunit/configs/all_tests.config
index 422e186cf3cf1..c1d3659a41cf0 100644
--- a/tools/testing/kunit/configs/all_tests.config
+++ b/tools/testing/kunit/configs/all_tests.config
@@ -44,10 +44,12 @@ CONFIG_REGMAP_BUILD=y
CONFIG_AUDIT=y
CONFIG_PRIME_NUMBERS=y
+CONFIG_CRC_ENABLE_ALL_FOR_KUNIT=y
+
CONFIG_SECURITY=y
CONFIG_SECURITY_APPARMOR=y
CONFIG_SECURITY_LANDLOCK=y
CONFIG_SOUND=y
--
2.53.0
next prev parent reply other threads:[~2026-04-21 21:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 21:05 [PATCH 6.18 0/8] Backport crypto and CRC KUnit improvements Eric Biggers
2026-04-21 21:05 ` [PATCH 6.18 1/8] lib/crc: tests: Make crc_kunit test only the enabled CRC variants Eric Biggers
2026-04-21 21:05 ` [PATCH 6.18 2/8] lib/crc: tests: Add CRC_ENABLE_ALL_FOR_KUNIT Eric Biggers
2026-04-21 21:05 ` [PATCH 6.18 3/8] lib/crc: tests: Add a .kunitconfig file Eric Biggers
2026-04-21 21:05 ` Eric Biggers [this message]
2026-04-21 21:05 ` [PATCH 6.18 5/8] lib/crypto: " Eric Biggers
2026-04-21 21:05 ` [PATCH 6.18 6/8] lib/crypto: tests: Introduce CRYPTO_LIB_ENABLE_ALL_FOR_KUNIT Eric Biggers
2026-04-21 21:05 ` [PATCH 6.18 7/8] kunit: configs: Enable all crypto library tests in all_tests.config Eric Biggers
2026-04-21 21:05 ` [PATCH 6.18 8/8] lib/crypto: tests: Drop the default to CRYPTO_SELFTESTS 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=20260421210554.36096-5-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=ardb@kernel.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-crypto@vger.kernel.org \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.