From: Akhil Goyal <gakhil@marvell.com>
To: Kai Ji <kai.ji@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>
Subject: RE: [EXT] [dpdk-dev v2] crypto/openssl: EVP_PKEY routine update in rsa op
Date: Tue, 5 Jul 2022 16:33:49 +0000 [thread overview]
Message-ID: <CO6PR18MB44842A7FB77B543F5DAB0487D8819@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20220705131625.40665-1-kai.ji@intel.com>
> EVP_PKEY function need to be called twice for rsa sign and verify
> operations in 3.0 EVP API, original openssl 1.x routines are
> untouched. The OPENSSL_API_COMPAT also removed as this branch code
> will be executed when Openssl 3.0 lib is detected on the host.
>
> Fixes: d7bd42f6db19 ("crypto/openssl: update RSA routine with 3.0 EVP API")
>
> Signed-off-by: Kai Ji <kai.ji@intel.com>
Applied again on dpdk-next-crypto
Reworded title and description.
Thanks.
prev parent reply other threads:[~2022-07-05 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 10:38 [dpdk-dev v1] " Kai Ji
2022-07-01 19:14 ` [EXT] " Akhil Goyal
2022-07-04 19:45 ` Thomas Monjalon
2022-07-05 10:43 ` Ji, Kai
2022-07-05 10:55 ` Thomas Monjalon
2022-07-05 13:16 ` [dpdk-dev v2] " Kai Ji
2022-07-05 16:33 ` Akhil Goyal [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=CO6PR18MB44842A7FB77B543F5DAB0487D8819@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=dev@dpdk.org \
--cc=kai.ji@intel.com \
--cc=thomas@monjalon.net \
/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).