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
Subject: Re: [PATCH 0/3] lib/crc: Fix crc_kunit dependency and add kunitconfig
Date: Fri, 13 Mar 2026 17:03:25 -0700 [thread overview]
Message-ID: <20260314000325.GA6574@quark> (raw)
In-Reply-To: <20260306033557.250499-1-ebiggers@kernel.org>
On Thu, Mar 05, 2026 at 07:35:54PM -0800, Eric Biggers wrote:
> This series fixes crc_kunit to follow the standard KUnit convention of
> depending on the code it tests rather than selecting it, adds a kconfig
> option that enables all the CRC variants for KUnit testing, and adds a
> kunitconfig file for lib/crc/.
>
> This follows similar changes to lib/crypto/ (except lib/crypto/ doesn't
> have an equivalent to CRC_ENABLE_ALL_FOR_KUNIT yet, but we could
> consider adding one).
>
> This series applies to v7.0-rc2 and is targeting crc-next.
>
> Eric Biggers (3):
> lib/crc: tests: Make crc_kunit test only the enabled CRC variants
> lib/crc: tests: Add CRC_ENABLE_ALL_FOR_KUNIT
> lib/crc: tests: Add a .kunitconfig file
>
> lib/crc/.kunitconfig | 3 +++
> lib/crc/Kconfig | 17 +++++++++++++----
> lib/crc/tests/crc_kunit.c | 28 ++++++++++++++++++++++------
> 3 files changed, 38 insertions(+), 10 deletions(-)
> create mode 100644 lib/crc/.kunitconfig
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-14 0:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 3:35 [PATCH 0/3] lib/crc: Fix crc_kunit dependency and add kunitconfig Eric Biggers
2026-03-06 3:35 ` [PATCH 1/3] lib/crc: tests: Make crc_kunit test only the enabled CRC variants Eric Biggers
2026-03-06 3:35 ` [PATCH 2/3] lib/crc: tests: Add CRC_ENABLE_ALL_FOR_KUNIT Eric Biggers
2026-03-06 3:35 ` [PATCH 3/3] lib/crc: tests: Add a .kunitconfig file Eric Biggers
2026-03-14 0:03 ` 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=20260314000325.GA6574@quark \
--to=ebiggers@kernel.org \
--cc=ardb@kernel.org \
--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