From: Eric Biggers <ebiggers@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: linux-crypto@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
kunit-dev@googlegroups.com,
Brendan Higgins <brendan.higgins@linux.dev>,
David Gow <david@davidgow.net>, Rae Moar <raemoar63@gmail.com>
Subject: Re: [PATCH] kunit: configs: Enable all CRC tests in all_tests.config
Date: Tue, 17 Mar 2026 09:30:01 -0700 [thread overview]
Message-ID: <20260317163001.GB2931@sol> (raw)
In-Reply-To: <20260314172224.15152-1-ebiggers@kernel.org>
On Sat, Mar 14, 2026 at 10:22:24AM -0700, Eric Biggers wrote:
> 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.
>
> Signed-off-by: Eric Biggers <ebiggers@kernel.org>
> ---
>
> This patch is targeting crc-next
> (https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git/log/?h=crc-next)
> which has the commit adding CONFIG_CRC_ENABLE_ALL_FOR_KUNIT.
>
> Note that patch also mirrors
> https://lore.kernel.org/linux-crypto/20260314035927.51351-3-ebiggers@kernel.org/
> which does the same for the crypto library tests.
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git/log/?h=crc-next
- Eric
prev parent reply other threads:[~2026-03-17 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-14 17:22 [PATCH] kunit: configs: Enable all CRC tests in all_tests.config Eric Biggers
2026-03-17 11:07 ` Ard Biesheuvel
2026-03-17 16:30 ` Eric Biggers [this message]
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=20260317163001.GB2931@sol \
--to=ebiggers@kernel.org \
--cc=ardb@kernel.org \
--cc=brendan.higgins@linux.dev \
--cc=david@davidgow.net \
--cc=kunit-dev@googlegroups.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raemoar63@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 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.