All of lore.kernel.org
 help / color / mirror / Atom feed
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, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] lib: Move crypto library tests to Runtime Testing menu
Date: Tue, 24 Mar 2026 16:27:43 -0700	[thread overview]
Message-ID: <20260324232743.GB3622@quark> (raw)
In-Reply-To: <20260322032438.286296-1-ebiggers@kernel.org>

On Sat, Mar 21, 2026 at 08:24:38PM -0700, Eric Biggers wrote:
> Currently the kconfig options for the crypto library KUnit tests appear
> in the menu:
> 
>     -> Library routines
>       -> Crypto library routines
> 
> However, this is the only content of "Crypto library routines".  I.e.,
> it is empty when CONFIG_KUNIT=n.  This is because the crypto library
> routines themselves don't have (or need to have) prompts.
> 
> Since this usually ends up as an unnecessary empty menu, let's remove
> this menu and instead source the lib/crypto/tests/Kconfig file from
> lib/Kconfig.debug inside the "Runtime Testing" menu:
> 
>     -> Kernel hacking
>       -> Kernel Testing and Coverage
>         -> Runtime Testing
> 
> This puts the prompts alongside the ones for most of the other lib/
> KUnit tests.  This seems to be a much better match to how the kconfig
> menus are organized.
> 
> Signed-off-by: Eric Biggers <ebiggers@kernel.org>
> ---
> 
> This patch is targeting the libcrypto-next tree
> 
>  lib/Kconfig.debug  | 2 ++
>  lib/crypto/Kconfig | 6 ------
>  2 files changed, 2 insertions(+), 6 deletions(-)

Applied to https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git/log/?h=libcrypto-next

- Eric

      parent reply	other threads:[~2026-03-24 23:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-22  3:24 [PATCH] lib: Move crypto library tests to Runtime Testing menu Eric Biggers
2026-03-22 20:08 ` Randy Dunlap
2026-03-24 23:27 ` 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=20260324232743.GB3622@quark \
    --to=ebiggers@kernel.org \
    --cc=Jason@zx2c4.com \
    --cc=ardb@kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@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.