From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"ruifeng.wang@arm.com" <ruifeng.wang@arm.com>,
"michaelsh@marvell.com" <michaelsh@marvell.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/5] cryptodev: remove list end enumerators
Date: Thu, 1 Oct 2020 09:49:35 +0000 [thread overview]
Message-ID: <SN6PR11MB28801CB2132114D9FA62F409E4300@SN6PR11MB2880.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200930173226.770-1-arkadiuszx.kusztal@intel.com>
> -----Original Message-----
> From: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>
> Sent: Wednesday, September 30, 2020 6:32 PM
> To: dev@dpdk.org
> Cc: akhil.goyal@nxp.com; Trahe, Fiona <fiona.trahe@intel.com>; ruifeng.wang@arm.com;
> michaelsh@marvell.com; Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>
> Subject: [PATCH v2 0/5] cryptodev: remove list end enumerators
>
> This patchset removes enumerators RTE_CRYPTO_CIPHER_LIST_END,
> RTE_CRYPTO_AUTH_LIST_END, RTE_CRYPTO_AEAD_LIST_END from symmetric
> crypto as well as RTE_CRYPTO_ASYM_XFORM_TYPE_LIST_END,
> RTE_CRYPTO_ASYM_OP_LIST_END, RTE_CRYPTO_RSA_PADDING_TYPE_LIST_END
> enumerators from asymmetric crypto API to prevent some problems that may
> arise when adding new crypto algorithms.
>
> This patchset depends on the following patches:
>
> [1] crypto/mvsam: remove crypto end enumerators
> (http://patchwork.dpdk.org/patch/79302/)
> [2] crypto/armv8: remove crypto enum list end references
> (http://patchwork.dpdk.org/patch/78070/)
>
> v2:
> - combined patches into one series
> - added removal of deprecation notice
>
> Arek Kusztal (5):
> app/test: remove list end references from asym crypto
> crypto/qat: remove asym list end references
> cryptodev: remove crypto list end enumerators
> cryptodev: remove list ends from asymmetric crypto api
> doc: remove crypto list end deprecation notice
>
> app/test/test_cryptodev_asym.c | 6 ++++--
> doc/guides/rel_notes/deprecation.rst | 5 -----
> drivers/crypto/qat/qat_asym.c | 5 -----
> lib/librte_cryptodev/rte_crypto_asym.h | 10 +++-------
> lib/librte_cryptodev/rte_crypto_sym.h | 12 +++---------
> 5 files changed, 10 insertions(+), 28 deletions(-)
>
> --
> 2.17.1
Series
Acked-by: Fiona Trahe <fiona.trahe@intel.com>
prev parent reply other threads:[~2020-10-01 9:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 17:32 Arek Kusztal
2020-09-30 17:32 ` [dpdk-dev] [PATCH v2 1/5] app/test: remove list end references from asym crypto Arek Kusztal
2020-09-30 17:32 ` [dpdk-dev] [PATCH v2 2/5] crypto/qat: remove asym list end references Arek Kusztal
2020-09-30 17:32 ` [dpdk-dev] [PATCH v2 3/5] cryptodev: remove crypto list end enumerators Arek Kusztal
2020-10-08 19:58 ` Akhil Goyal
2020-10-12 5:15 ` Kusztal, ArkadiuszX
2020-10-12 11:46 ` Akhil Goyal
2020-09-30 17:32 ` [dpdk-dev] [PATCH v2 4/5] cryptodev: remove list ends from asymmetric crypto api Arek Kusztal
2020-10-08 19:51 ` Akhil Goyal
2020-10-09 7:02 ` Kusztal, ArkadiuszX
2020-09-30 17:32 ` [dpdk-dev] [PATCH v2 5/5] doc: remove crypto list end deprecation notice Arek Kusztal
2020-10-01 9:49 ` Trahe, Fiona [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=SN6PR11MB28801CB2132114D9FA62F409E4300@SN6PR11MB2880.namprd11.prod.outlook.com \
--to=fiona.trahe@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=michaelsh@marvell.com \
--cc=ruifeng.wang@arm.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).