From: Ignat Korchagin <ignat@cloudflare.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: lei he <helei.sig11@bytedance.com>, kernel-team@cloudflare.com
Subject: [PATCH 4/4] crypto: remove unused field in pkcs8_parse_context
Date: Thu, 8 Sep 2022 21:00:36 +0100 [thread overview]
Message-ID: <20220908200036.2034-5-ignat@cloudflare.com> (raw)
In-Reply-To: <20220908200036.2034-1-ignat@cloudflare.com>
From: lei he <helei.sig11@bytedance.com>
remove unused field 'algo_oid' in pkcs8_parse_context
Signed-off-by: lei he <helei.sig11@bytedance.com>
---
crypto/asymmetric_keys/pkcs8_parser.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/crypto/asymmetric_keys/pkcs8_parser.c b/crypto/asymmetric_keys/pkcs8_parser.c
index e507c635ead5..f81317234331 100644
--- a/crypto/asymmetric_keys/pkcs8_parser.c
+++ b/crypto/asymmetric_keys/pkcs8_parser.c
@@ -21,7 +21,6 @@ struct pkcs8_parse_context {
struct public_key *pub;
unsigned long data; /* Start of data */
enum OID last_oid; /* Last OID encountered */
- enum OID algo_oid; /* Algorithm OID */
u32 key_size;
const void *key;
const void *algo_param;
--
2.36.1
next prev parent reply other threads:[~2022-09-08 20:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 20:00 [PATCH 0/4] crypto: add ECDSA signature support to key retention service Ignat Korchagin
2022-09-08 20:00 ` [PATCH 1/4] crypto: add ECDSA signature generation support Ignat Korchagin
2022-09-08 20:00 ` [PATCH 2/4] crypto: add ECDSA test vectors from RFC 6979 Ignat Korchagin
2022-09-08 20:00 ` [PATCH 3/4] crypto: pkcs8 parser support ECDSA private keys Ignat Korchagin
2022-09-08 20:00 ` Ignat Korchagin [this message]
2022-09-24 7:24 ` [PATCH 0/4] crypto: add ECDSA signature support to key retention service Herbert Xu
2022-09-27 21:18 ` Ignat Korchagin
2022-09-28 7:51 ` 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=20220908200036.2034-5-ignat@cloudflare.com \
--to=ignat@cloudflare.com \
--cc=davem@davemloft.net \
--cc=helei.sig11@bytedance.com \
--cc=herbert@gondor.apana.org.au \
--cc=kernel-team@cloudflare.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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.