From: Akhil Goyal <gakhil@marvell.com>
To: "hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
Anoob Joseph <anoobj@marvell.com>,
"pablo.de.lara.guarch@intel.com" <pablo.de.lara.guarch@intel.com>,
"fiona.trahe@intel.com" <fiona.trahe@intel.com>,
"declan.doherty@intel.com" <declan.doherty@intel.com>,
"matan@nvidia.com" <matan@nvidia.com>,
"g.singh@nxp.com" <g.singh@nxp.com>,
"fanzhang.oss@gmail.com" <fanzhang.oss@gmail.com>,
"jianjay.zhou@huawei.com" <jianjay.zhou@huawei.com>,
"asomalap@amd.com" <asomalap@amd.com>,
"ruifeng.wang@arm.com" <ruifeng.wang@arm.com>,
"konstantin.v.ananyev@yandex.ru" <konstantin.v.ananyev@yandex.ru>,
"radu.nicolau@intel.com" <radu.nicolau@intel.com>,
"ajit.khaparde@broadcom.com" <ajit.khaparde@broadcom.com>,
Nagadheeraj Rottela <rnagadheeraj@marvell.com>,
Ankur Dwivedi <adwivedi@marvell.com>,
"ciara.power@intel.com" <ciara.power@intel.com>
Subject: RE: [EXT] Re: [PATCH] cryptodev: remove deprecated algo string arrays
Date: Tue, 19 Sep 2023 13:28:01 +0000 [thread overview]
Message-ID: <CO6PR18MB4484F7E62C14734048174B9BD8FAA@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <9c38e2e3-a5e3-e24d-bb3e-b9d0f7c18f6a@oss.nxp.com>
> Acked-by: Hemant Agrawal<hemant.agrawal@nxp.com>
>
> >
> > Removed the algorithm strings arrays ``rte_crypto_cipher_algorithm_strings``,
> > ``rte_crypto_auth_algorithm_strings``, ``rte_crypto_aead_algorithm_strings``
> > and ``rte_crypto_asym_xform_strings``.
> > Application can use the new APIs ``rte_cryptodev_get_cipher_algo_string``,
> > ``rte_cryptodev_get_auth_algo_string``,
> ``rte_cryptodev_get_aead_algo_string``
> > and ``rte_cryptodev_asym_get_xform_string`` respectively.
> >
> > Signed-off-by: Akhil Goyal <gakhil@marvell.com>
> > ---
> >
> > Release notes will be updated when base patch is merged.
> >
> > doc/guides/rel_notes/deprecation.rst | 7 --
> > lib/cryptodev/rte_crypto_asym.h | 5 --
> > lib/cryptodev/rte_crypto_sym.h | 15 ----
> > lib/cryptodev/rte_cryptodev.c | 108 ---------------------------
> > lib/cryptodev/version.map | 4 -
> > 5 files changed, 139 deletions(-)
> >
> > diff --git a/doc/guides/rel_notes/deprecation.rst
> b/doc/guides/rel_notes/deprecation.rst
> > index 494b401cda..2f3738fdea 100644
> > --- a/doc/guides/rel_notes/deprecation.rst
> > +++ b/doc/guides/rel_notes/deprecation.rst
> > @@ -177,13 +177,6 @@ Deprecation Notices
> > which got error interrupt to the application,
> > so that application can reset that particular queue pair.
> >
> > -* cryptodev: The arrays of algorithm strings
> ``rte_crypto_cipher_algorithm_strings``,
> > - ``rte_crypto_auth_algorithm_strings``,
> ``rte_crypto_aead_algorithm_strings`` and
> > - ``rte_crypto_asym_xform_strings`` are deprecated and will be removed in
> DPDK 23.11.
> > - Application can use the new APIs ``rte_cryptodev_get_cipher_algo_string``,
> > - ``rte_cryptodev_get_auth_algo_string``,
> ``rte_cryptodev_get_aead_algo_string`` and
> > - ``rte_cryptodev_asym_get_xform_string`` respectively.
> > -
Applied to dpdk-next-crypto
Updated release notes for the removal of the arrays.
prev parent reply other threads:[~2023-09-19 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 3:37 Akhil Goyal
2023-07-31 6:18 ` Hemant Agrawal
2023-09-19 13:28 ` 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=CO6PR18MB4484F7E62C14734048174B9BD8FAA@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=adwivedi@marvell.com \
--cc=ajit.khaparde@broadcom.com \
--cc=anoobj@marvell.com \
--cc=asomalap@amd.com \
--cc=ciara.power@intel.com \
--cc=david.marchand@redhat.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=fiona.trahe@intel.com \
--cc=g.singh@nxp.com \
--cc=hemant.agrawal@nxp.com \
--cc=jianjay.zhou@huawei.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=matan@nvidia.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=radu.nicolau@intel.com \
--cc=rnagadheeraj@marvell.com \
--cc=ruifeng.wang@arm.com \
--cc=thomas@monjalon.net \
/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).