From: Akhil Goyal <gakhil@marvell.com>
To: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"arkadiuszx.kusztal@intel.com" <arkadiuszx.kusztal@intel.com>,
Fan Zhang <fanzhang.oss@gmail.com>
Cc: Anoob Joseph <anoobj@marvell.com>,
"FanZhangfanzhang.oss@gmail.com" <FanZhangfanzhang.oss@gmail.com>,
Kai Ji <kai.ji@intel.com>, Jerin Jacob <jerinj@marvell.com>,
Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Subject: RE: [PATCH v3 1/3] cryptodev: add asymmetric operational capability
Date: Wed, 9 Oct 2024 20:29:09 +0000 [thread overview]
Message-ID: <CO6PR18MB44842384A5103AE918689CBCD87F2@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20241009071151.1106-1-gmuthukrishn@marvell.com>
> Subject: [PATCH v3 1/3] cryptodev: add asymmetric operational capability
>
> Asymmetric crypto algorithms such as SM2, EdDSA would need per op
> capability and based on it, the input param to a crypto operation
> is chosen wisely.
>
> Signed-off-by: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
> ---
> v3:
> - Removed unused rte_crypto_sm2_op_capa enum value
> RTE_CRYPTO_SM2_PKE_KDF.
> HW that needs it can add this enum.
> - Test and driver changes split from it and follows within same series.
Series acked-by: Akhil Goyal <gakhil@marvell.com>
Arek's ack taken from v2.
Updated release notes
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2024-10-09 20:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 18:17 [PATCH] " Gowrishankar Muthukrishnan
2024-10-04 18:12 ` [PATCH v2] " Gowrishankar Muthukrishnan
2024-10-08 17:06 ` Kusztal, ArkadiuszX
2024-10-09 3:38 ` Gowrishankar Muthukrishnan
2024-10-09 7:11 ` [PATCH v3 1/3] " Gowrishankar Muthukrishnan
2024-10-09 7:11 ` [PATCH v3 2/3] test/crypto: check op capabilities in SM2 tests Gowrishankar Muthukrishnan
2024-10-09 7:11 ` [PATCH v3 3/3] crypto/openssl: include op capabilities for SM2 Gowrishankar Muthukrishnan
2024-10-09 20:29 ` 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=CO6PR18MB44842384A5103AE918689CBCD87F2@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=FanZhangfanzhang.oss@gmail.com \
--cc=anoobj@marvell.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=gmuthukrishn@marvell.com \
--cc=jerinj@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).