From: Lei He <helei.sig11@bytedance.com>
To: herbert@gondor.apana.org.au, davem@davemloft.net,
dhowells@redhat.com, mst@redhat.com
Cc: arei.gonglei@huawei.com, jasowang@redhat.com,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
pizhenwei@bytedance.com, helei.sig11@bytedance.com,
f4bug@amsat.org, berrange@redhat.com
Subject: [PATCH 3/4] crypto: remove unused field in pkcs8_parse_context
Date: Fri, 17 Jun 2022 15:07:53 +0800 [thread overview]
Message-ID: <20220617070754.73667-5-helei.sig11@bytedance.com> (raw)
In-Reply-To: <20220617070754.73667-1-helei.sig11@bytedance.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.20.1
next prev parent reply other threads:[~2022-06-17 7:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 7:07 [PATCH 0/4] virtio-crypto: support ECDSA algorithm Lei He
2022-06-17 7:07 ` [PATCH 1/4] crypto: fix the calculation of max_size for ECDSA Lei He
2022-06-17 7:07 ` [PATCH] crypto: testmgr - fix version number of RSA tests Lei He
2022-06-19 7:09 ` Michael S. Tsirkin
2022-06-20 2:57 ` [External] " 何磊
2022-06-17 7:07 ` [PATCH 2/4] crypto: pkcs8 parser support ECDSA private keys Lei He
2022-06-17 7:07 ` Lei He [this message]
2022-06-17 7:07 ` [PATCH 4/4] virtio-crypto: support ECDSA algorithm Lei He
2022-06-17 14:40 ` kernel test robot
2022-06-17 17:27 ` kernel test robot
2022-06-17 11:02 ` [PATCH 0/4] " Michael S. Tsirkin
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=20220617070754.73667-5-helei.sig11@bytedance.com \
--to=helei.sig11@bytedance.com \
--cc=arei.gonglei@huawei.com \
--cc=berrange@redhat.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=f4bug@amsat.org \
--cc=herbert@gondor.apana.org.au \
--cc=jasowang@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pizhenwei@bytedance.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).