From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Herbert Xu" <herbert@gondor.apana.org.au>,
"Joachim Vandersmissen" <git@jvdsn.com>
Cc: <linux-crypto@vger.kernel.org>,
"David Howells" <dhowells@redhat.com>,
"Simo Sorce" <simo@redhat.com>,
"Stephan Mueller" <smueller@chronox.de>
Subject: Re: [PATCH v3 1/2] certs: Move RSA self-test data to separate file
Date: Fri, 10 May 2024 11:41:49 +0300 [thread overview]
Message-ID: <D15TX19UXQSW.34JYJLN21P1RH@kernel.org> (raw)
In-Reply-To: <Zj3XtsHcwRAv_EvT@gondor.apana.org.au>
On Fri May 10, 2024 at 11:15 AM EEST, Herbert Xu wrote:
> On Thu, May 02, 2024 at 11:38:56PM -0500, Joachim Vandersmissen wrote:
> >
> > diff --git a/crypto/asymmetric_keys/Kconfig b/crypto/asymmetric_keys/Kconfig
> > index 59ec726b7c77..68434c745b3c 100644
> > --- a/crypto/asymmetric_keys/Kconfig
> > +++ b/crypto/asymmetric_keys/Kconfig
> > @@ -86,4 +86,14 @@ config FIPS_SIGNATURE_SELFTEST
> > depends on PKCS7_MESSAGE_PARSER=X509_CERTIFICATE_PARSER
> > depends on X509_CERTIFICATE_PARSER
> >
> > +config FIPS_SIGNATURE_SELFTEST_RSA
> > + bool "Include RSA selftests"
>
> Please don't ask questinons in Kconfig that we can avoid. In
> this case I see no valid reason for having this extra knob.
>
> One question for FIPS_SIGNATURE_SELFTEST is enough.
>
> Oh and please cc Jarkko Sakkinen <jarkko@kernel.org> since he
> picked up two earlier fixes for this and it's best if this went
> through his tree.
>
> Thanks,
Fine with me. I've yet to send asymmetric keys pull request (last
remaining) so there is some window left too.
BR, Jarkko
next prev parent reply other threads:[~2024-05-10 8:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 4:38 [PATCH v3 1/2] certs: Move RSA self-test data to separate file Joachim Vandersmissen
2024-05-03 4:38 ` [PATCH v3 2/2] certs: Add ECDSA signature verification self-test Joachim Vandersmissen
2024-05-10 8:15 ` [PATCH v3 1/2] certs: Move RSA self-test data to separate file Herbert Xu
2024-05-10 8:41 ` Jarkko Sakkinen [this message]
2024-05-10 13:18 ` Joachim Vandersmissen
2024-05-10 13:26 ` Herbert Xu
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=D15TX19UXQSW.34JYJLN21P1RH@kernel.org \
--to=jarkko@kernel.org \
--cc=dhowells@redhat.com \
--cc=git@jvdsn.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=simo@redhat.com \
--cc=smueller@chronox.de \
/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;
as well as URLs for NNTP newsgroup(s).