From: Anoob Joseph <anoobj@marvell.com>
To: Akhil Goyal <gakhil@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "ciara.power@intel.com" <ciara.power@intel.com>,
"fanzhang.oss@gmail.com" <fanzhang.oss@gmail.com>,
"kai.ji@intel.com" <kai.ji@intel.com>,
"pablo.de.lara.guarch@intel.com" <pablo.de.lara.guarch@intel.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"matan@nvidia.com" <matan@nvidia.com>,
"g.singh@nxp.com" <g.singh@nxp.com>,
"ruifeng.wang@arm.com" <ruifeng.wang@arm.com>,
"radu.nicolau@intel.com" <radu.nicolau@intel.com>,
Volodymyr Fialko <vfialko@marvell.com>,
"ktraynor@redhat.com" <ktraynor@redhat.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
Akhil Goyal <gakhil@marvell.com>
Subject: RE: [PATCH] cryptodev: add algo enums to string conversion APIs
Date: Tue, 13 Dec 2022 07:37:50 +0000 [thread overview]
Message-ID: <SA1PR18MB4661FF9EED919C8A69F9CC5ADFE39@SA1PR18MB4661.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20221212151023.3308146-1-gakhil@marvell.com>
>
> Symmetric/Asymmetric algorithm strings are accessed by application using
> arrays in cryptodev lib, which hampers new algorithms addition in the array
> due to ABI breakage.
> These arrays are now deprecated and will be removed in next ABI break
> release.
> New APIs are added for getting the algorithm strings based on enum values.
>
> Signed-off-by: Akhil Goyal <gakhil@marvell.com>
Acked-by: Anoob Joseph <anoobj@marvell.com>
next prev parent reply other threads:[~2022-12-13 7:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 15:10 Akhil Goyal
2022-12-13 7:31 ` Ruifeng Wang
2022-12-13 7:37 ` Anoob Joseph [this message]
2022-12-13 8:22 ` Power, Ciara
2022-12-14 9:32 ` Zhang, Fan
2023-01-04 6:18 ` [PATCH v2] " Akhil Goyal
2023-01-05 10:56 ` 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=SA1PR18MB4661FF9EED919C8A69F9CC5ADFE39@SA1PR18MB4661.namprd18.prod.outlook.com \
--to=anoobj@marvell.com \
--cc=ciara.power@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=g.singh@nxp.com \
--cc=gakhil@marvell.com \
--cc=hemant.agrawal@nxp.com \
--cc=kai.ji@intel.com \
--cc=ktraynor@redhat.com \
--cc=matan@nvidia.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=radu.nicolau@intel.com \
--cc=ruifeng.wang@arm.com \
--cc=thomas@monjalon.net \
--cc=vfialko@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).