From: "Ji, Kai" <kai.ji@intel.com>
To: Ashwin Sekhar T K <asekhar@marvell.com>
Cc: "anoobj@marvell.com" <anoobj@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"gakhil@marvell.com" <gakhil@marvell.com>,
"hkalra@marvell.com" <hkalra@marvell.com>,
"jerinj@marvell.com" <jerinj@marvell.com>,
"kirankumark@marvell.com" <kirankumark@marvell.com>,
"ndabilpuram@marvell.com" <ndabilpuram@marvell.com>,
"pbhagavatula@marvell.com" <pbhagavatula@marvell.com>,
"psatheesh@marvell.com" <psatheesh@marvell.com>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"skori@marvell.com" <skori@marvell.com>,
"skoteshwar@marvell.com" <skoteshwar@marvell.com>
Subject: RE: [PATCH v5 1/1] crypto/openssl: support aes cmac operations
Date: Mon, 18 Jul 2022 16:54:45 +0000 [thread overview]
Message-ID: <SN6PR11MB3408245A3B68CA5D4565F037818C9@SN6PR11MB3408.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220718162521.94787-2-asekhar@marvell.com>
> -----Original Message-----
> From: Ashwin Sekhar T K <asekhar@marvell.com>
> Sent: Monday, July 18, 2022 5:25 PM
> To: asekhar@marvell.com
> Cc: anoobj@marvell.com; dev@dpdk.org; gakhil@marvell.com;
> hkalra@marvell.com; jerinj@marvell.com; kirankumark@marvell.com;
> ndabilpuram@marvell.com; pbhagavatula@marvell.com;
> psatheesh@marvell.com; Zhang, Roy Fan <roy.fan.zhang@intel.com>;
> skori@marvell.com; skoteshwar@marvell.com
> Subject: [PATCH v5 1/1] crypto/openssl: support aes cmac operations
>
> Extend openssl crypto PMD to support AES CMAC operations.
>
> Signed-off-by: Ashwin Sekhar T K <asekhar@marvell.com>
> ---
Acked-by: Kai Ji <kai.ji@intel.com>
next prev parent reply other threads:[~2022-07-18 16:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 16:28 [PATCH] crypto/openssl: support " Ashwin Sekhar T K
2022-06-17 10:11 ` Zhang, Roy Fan
2022-07-18 6:07 ` [PATCH v2 0/1] crypto/openssl: add aes cmac support Ashwin Sekhar T K
2022-07-18 6:07 ` [PATCH v2 1/1] crypto/openssl: support aes cmac operations Ashwin Sekhar T K
2022-07-18 9:12 ` [PATCH v3 0/1] crypto/openssl: add aes cmac support Ashwin Sekhar T K
2022-07-18 9:12 ` [PATCH v3 1/1] crypto/openssl: support aes cmac operations Ashwin Sekhar T K
2022-07-18 9:18 ` [PATCH v4 0/1] crypto/openssl: add aes cmac support Ashwin Sekhar T K
2022-07-18 9:18 ` [PATCH v4 1/1] crypto/openssl: support aes cmac operations Ashwin Sekhar T K
2022-07-18 16:25 ` [PATCH v5 0/1] crypto/openssl: add aes cmac support Ashwin Sekhar T K
2022-07-18 16:25 ` [PATCH v5 1/1] crypto/openssl: support aes cmac operations Ashwin Sekhar T K
2022-07-18 16:54 ` Ji, Kai [this message]
2022-08-26 8:52 ` Akhil Goyal
2022-07-18 13:57 ` [PATCH v4 0/1] crypto/openssl: add aes cmac support Ji, Kai
2022-07-18 16:18 ` Ashwin Sekhar Thalakalath Kottilveetil
2022-06-30 15:41 ` [PATCH v2] crypto/ipsec_mb: enable support for arm64 Ashwin Sekhar T K
2022-07-04 14:47 ` Zhang, Roy Fan
2022-07-27 8:29 ` Ruifeng Wang
2022-07-27 8:48 ` Ashwin Sekhar Thalakalath Kottilveetil
2022-08-26 8:45 ` Akhil Goyal
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=SN6PR11MB3408245A3B68CA5D4565F037818C9@SN6PR11MB3408.namprd11.prod.outlook.com \
--to=kai.ji@intel.com \
--cc=anoobj@marvell.com \
--cc=asekhar@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=hkalra@marvell.com \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=psatheesh@marvell.com \
--cc=roy.fan.zhang@intel.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.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).