From: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
To: Ashwin Sekhar T K <asekhar@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "jerinj@marvell.com" <jerinj@marvell.com>,
"skori@marvell.com" <skori@marvell.com>,
"skoteshwar@marvell.com" <skoteshwar@marvell.com>,
"pbhagavatula@marvell.com" <pbhagavatula@marvell.com>,
"kirankumark@marvell.com" <kirankumark@marvell.com>,
"psatheesh@marvell.com" <psatheesh@marvell.com>,
"anoobj@marvell.com" <anoobj@marvell.com>,
"gakhil@marvell.com" <gakhil@marvell.com>,
"hkalra@marvell.com" <hkalra@marvell.com>,
"ndabilpuram@marvell.com" <ndabilpuram@marvell.com>
Subject: RE: [PATCH] crypto/openssl: support cmac operations
Date: Fri, 17 Jun 2022 10:11:43 +0000 [thread overview]
Message-ID: <PH7PR11MB581775EDEC4B88CC000EC8B4B8AF9@PH7PR11MB5817.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220610162836.1828084-1-asekhar@marvell.com>
Hi,
> -----Original Message-----
> From: Ashwin Sekhar T K <asekhar@marvell.com>
> Sent: Friday, June 10, 2022 5:29 PM
> To: dev@dpdk.org
> Cc: jerinj@marvell.com; skori@marvell.com; skoteshwar@marvell.com;
> pbhagavatula@marvell.com; kirankumark@marvell.com;
> psatheesh@marvell.com; asekhar@marvell.com; anoobj@marvell.com;
> gakhil@marvell.com; hkalra@marvell.com; ndabilpuram@marvell.com
> Subject: [PATCH] crypto/openssl: support cmac operations
>
> Extend openssl crypto PMD to support CMAC operations.
>
> Signed-off-by: Ashwin Sekhar T K <asekhar@marvell.com>
> ---
Although the patch passes all tests in openssl 1.1, but I see 95 tests failed on openssl 3.0.
Can you check that?
Regards,
Fan
next prev parent reply other threads:[~2022-06-17 10:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 16:28 [PATCH] crypto/openssl: support cmac operations Ashwin Sekhar T K
2022-06-17 10:11 ` Zhang, Roy Fan [this message]
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
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=PH7PR11MB581775EDEC4B88CC000EC8B4B8AF9@PH7PR11MB5817.namprd11.prod.outlook.com \
--to=roy.fan.zhang@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=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 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.