From: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
To: "Ji, Kai" <kai.ji@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Ji, Kai" <kai.ji@intel.com>, "gakhil@marvell.com" <gakhil@marvell.com>
Subject: RE: [dpdk-dev v2] crypto/openssl: openssl 3.0 support on sym MAC routine
Date: Mon, 7 Feb 2022 15:40:17 +0000 [thread overview]
Message-ID: <MW5PR11MB5809BC9EFD9083F4ABA5E875B82C9@MW5PR11MB5809.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220207152410.53244-1-kai.ji@intel.com>
> -----Original Message-----
> From: Kai Ji <kai.ji@intel.com>
> Sent: Monday, February 7, 2022 3:24 PM
> To: dev@dpdk.org
> Cc: Ji, Kai <kai.ji@intel.com>
> Subject: [dpdk-dev v2] crypto/openssl: openssl 3.0 support on sym MAC
> routine
>
> This patch update the symmetric EVP MAC routine in crypto openssl pmd
> to adopt openssl 3.0 library.
>
> Signed-off-by: Kai Ji <kai.ji@intel.com>
>
> v2:
> - commit message update
>
> ---
Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
next prev parent reply other threads:[~2022-02-07 15:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 17:57 [dpdk-dev v1] crypto/openssl: openssl EVP MAC routine api update Kai Ji
2022-02-07 15:24 ` [dpdk-dev v2] crypto/openssl: openssl 3.0 support on sym MAC routine Kai Ji
2022-02-07 15:40 ` Zhang, Roy Fan [this message]
2022-02-17 17:45 ` [dpdk-dev v3] crypto/openssl: openssl 3.0 support on sym crypto routine Kai Ji
2022-02-17 18:01 ` [EXT] " Akhil Goyal
2022-02-18 9:44 ` [dpdk-dev v4] " Kai Ji
2022-02-18 11:51 ` [dpdk-dev v5] " Kai Ji
2022-02-18 13:41 ` Zhang, Roy Fan
2022-02-24 19:02 ` [EXT] " Akhil Goyal
2022-02-24 23:13 ` Ji, Kai
2022-02-25 3:55 ` Akhil Goyal
2022-02-25 10:19 ` Ji, Kai
2022-02-25 10:39 ` Akhil Goyal
2022-02-25 11:19 ` Ji, Kai
2022-02-25 13:51 ` Zhang, Roy Fan
2022-02-28 5:35 ` Namburu, Chandu-babu
2022-02-25 15:13 ` [dpdk-dev v6] " Kai Ji
2022-02-25 17:35 ` Stephen Hemminger
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=MW5PR11MB5809BC9EFD9083F4ABA5E875B82C9@MW5PR11MB5809.namprd11.prod.outlook.com \
--to=roy.fan.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=kai.ji@intel.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).