From: David Howells <dhowells@redhat.com>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: dhowells@redhat.com, Stefan Berger <stefanb@linux.ibm.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
keyrings@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, patrick@puiterwijk.org,
linux-integrity@vger.kernel.org,
Mimi Zohar <zohar@linux.vnet.ibm.com>
Subject: Re: [PATCH v5 2/4] x509: Detect sm2 keys by their parameters OID
Date: Mon, 01 Feb 2021 15:07:35 +0000 [thread overview]
Message-ID: <4170408.1612192055@warthog.procyon.org.uk> (raw)
In-Reply-To: <58935b00f65e389e9ae3da2425d06bd88d280e43.camel@linux.ibm.com>
Mimi Zohar <zohar@linux.ibm.com> wrote:
> > > Do you have a branch you want me to pull or did you want me to take just
> > > patches 2-4?
> >
> > Please take it from the mailing list. If there are requests for more
> > changes on the crypto level, I will send another series. I personally am
> > waiting for some sort of verdict on the crypto level...
>
> The entire patch set should be upstreamed as a single patch set, after
> having each of the maintainer's Ack it. In addition, the v6 version is
> missing some Reviewed-by tags. (Stefan will re-post a v7 patch set.)
>
> David, I don't have problem with this patch set being upstreamed via
> the keys subsystem, assuming it's been tested.
Herbert wants the first patch to go through the crypto tree. Maybe all of
them should proceed by that route if Herbert is willing?
What do patches 2-4 do if patch 1 isn't applied?
David
next prev parent reply other threads:[~2021-02-01 15:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210129150355.850093-1-stefanb@linux.vnet.ibm.com>
[not found] ` <20210129150355.850093-2-stefanb@linux.vnet.ibm.com>
2021-01-29 19:44 ` [PATCH v5 1/4] crypto: Add support for ECDSA signature verification Herbert Xu
[not found] ` <20210129150355.850093-5-stefanb@linux.vnet.ibm.com>
[not found] ` <20210129155529.brxbmgzzosvtwrzw@altlinux.org>
2021-02-01 13:19 ` [PATCH v5 4/4] ima: Support EC keys for " David Howells
[not found] ` <20210129150355.850093-3-stefanb@linux.vnet.ibm.com>
2021-02-01 13:23 ` [PATCH v5 2/4] x509: Detect sm2 keys by their parameters OID David Howells
2021-02-01 14:35 ` Stefan Berger
2021-02-01 14:54 ` Mimi Zohar
2021-02-01 15:07 ` David Howells [this message]
2021-02-02 3:56 ` Herbert Xu
2021-02-02 8:27 ` David Howells
2021-02-02 8:55 ` Herbert Xu
2021-02-02 9:33 ` David Howells
2021-02-02 9:42 ` Herbert Xu
2021-02-02 10:16 ` David Howells
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=4170408.1612192055@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--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 \
--cc=zohar@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