From: David Howells <dhowells@redhat.com>
To: Stefan Berger <stefanb@linux.ibm.com>
Cc: dhowells@redhat.com, keyrings@vger.kernel.org,
linux-crypto@vger.kernel.org, davem@davemloft.net,
herbert@gondor.apana.org.au, zohar@linux.ibm.com,
linux-kernel@vger.kernel.org, patrick@puiterwijk.org,
linux-integrity@vger.kernel.org
Subject: Re: [PATCH v7 0/4] Add support for x509 certs with NIST p256 and p192 keys
Date: Mon, 01 Feb 2021 16:13:23 +0000 [thread overview]
Message-ID: <32177.1612196003@warthog.procyon.org.uk> (raw)
In-Reply-To: <20210201151910.1465705-1-stefanb@linux.ibm.com>
Stefan Berger <stefanb@linux.ibm.com> wrote:
> v6->v7:
> - Moved some OID defintions to patch 1 for bisectability
> - Applied R-b's
But I can't now apply 2-4 without patch 1.
David
next prev parent reply other threads:[~2021-02-01 16:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 15:19 [PATCH v7 0/4] Add support for x509 certs with NIST p256 and p192 keys Stefan Berger
2021-02-01 15:19 ` [PATCH v7 1/4] crypto: Add support for ECDSA signature verification Stefan Berger
2021-02-04 5:27 ` Herbert Xu
2021-02-04 5:43 ` Stefan Berger
2021-02-04 14:58 ` Jarkko Sakkinen
2021-02-01 15:19 ` [PATCH v7 2/4] x509: Detect sm2 keys by their parameters OID Stefan Berger
2021-02-01 15:19 ` [PATCH v7 3/4] x509: Add support for parsing x509 certs with ECDSA keys Stefan Berger
2021-02-11 8:03 ` kernel test robot
2021-02-11 17:30 ` Stefan Berger
2021-02-11 18:18 ` Stefan Berger
2021-02-01 15:19 ` [PATCH v7 4/4] ima: Support EC keys for signature verification Stefan Berger
2021-02-05 12:24 ` Mimi Zohar
2021-02-01 16:13 ` David Howells [this message]
2021-02-01 16:28 ` [PATCH v7 0/4] Add support for x509 certs with NIST p256 and p192 keys Stefan Berger
2021-02-01 16:36 ` David Howells
2021-02-01 16:45 ` Stefan Berger
2021-02-02 3:59 ` 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=32177.1612196003@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick@puiterwijk.org \
--cc=stefanb@linux.ibm.com \
--cc=zohar@linux.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).