From: Stefan Berger <stefanb@linux.ibm.com>
To: David Howells <dhowells@redhat.com>
Cc: Stefan Berger <stefanb@linux.vnet.ibm.com>,
keyrings@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, patrick@puiterwijk.org
Subject: Re: [PATCH v4 0/3] Add support for x509 certs with NIST p256 and p192 keys
Date: Thu, 28 Jan 2021 08:58:03 -0500 [thread overview]
Message-ID: <159fe247-b8c9-c718-1c2d-76cfb637f6dc@linux.ibm.com> (raw)
In-Reply-To: <3561487.1611842073@warthog.procyon.org.uk>
On 1/28/21 8:54 AM, David Howells wrote:
> Stefan Berger <stefanb@linux.ibm.com> wrote:
>
>>> This (sub)set is intended to go through the keyrings tree or is it all going
>>> through the crypto tree now?
>>
>> Patch 1/3 should go through 'crypto', the other ones through 'keyrings'.
> Do 2 & 3 depend on 1?
Functionality-wise, yes, compilation-wise, no.
Stefan
prev parent reply other threads:[~2021-01-28 13:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 0:14 [PATCH v4 0/3] Add support for x509 certs with NIST p256 and p192 keys Stefan Berger
2021-01-28 0:14 ` [PATCH v4 1/3] crypto: Add support for ECDSA signature verification Stefan Berger
2021-01-29 1:34 ` Herbert Xu
2021-01-28 0:14 ` [PATCH v4 2/3] x509: Detect sm2 keys by their parameters OID Stefan Berger
2021-01-28 0:14 ` [PATCH v4 3/3] x509: Add support for parsing x509 certs with ECDSA keys Stefan Berger
2021-01-28 9:19 ` [PATCH v4 0/3] Add support for x509 certs with NIST p256 and p192 keys David Howells
2021-01-28 13:45 ` Stefan Berger
2021-01-28 13:54 ` David Howells
2021-01-28 13:58 ` Stefan Berger [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=159fe247-b8c9-c718-1c2d-76cfb637f6dc@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=dhowells@redhat.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick@puiterwijk.org \
--cc=stefanb@linux.vnet.ibm.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 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).