From: David Marchand <david.marchand@redhat.com>
To: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Cc: dev <dev@dpdk.org>, Akhil Goyal <akhil.goyal@nxp.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>,
Anoob Joseph <anoobj@marvell.com>,
shallyv@marvell.com, Declan Doherty <declan.doherty@intel.com>,
Fan Zhang <roy.fan.zhang@intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [PATCH] [RFC] doc: announce removal of crypto list end enumerators
Date: Wed, 29 Jul 2020 17:24:25 +0200 [thread overview]
Message-ID: <CAJFAV8x0fHAA8zegMiuFN5pCKkNtxpWW-jzYq9Z35u-2oBtGhA@mail.gmail.com> (raw)
In-Reply-To: <20200729144651.17524-1-arkadiuszx.kusztal@intel.com>
On Wed, Jul 29, 2020 at 4:47 PM Arek Kusztal
<arkadiuszx.kusztal@intel.com> wrote:
>
> Enumerators RTE_CRYPTO_CIPHER_LIST_END, RTE_CRYPTO_AUTH_LIST_END,
> RTE_CRYPTO_AEAD_LIST_END will be removed to prevent some problems
> that may arise when adding new algorithms.
How does it cohabitate with Ferruh notice?
Is it a complement? or redundant?
https://git.dpdk.org/dpdk/commit/doc/guides/rel_notes/deprecation.rst?id=58245da070289f4b248f15970c3f8af73ea601ed
>
> Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> ---
> doc/guides/rel_notes/deprecation.rst | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index a58a179..34b0e3c 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -142,3 +142,9 @@ Deprecation Notices
> Python 2 support will be completely removed in 20.11.
> In 20.08, explicit deprecation warnings will be displayed when running
> scripts with Python 2.
> +
> +* cryptodev: ``RTE_CRYPTO_AEAD_LIST_END`` from ``enum rte_crypto_aead_algorithm``,
> + ``RTE_CRYPTO_CIPHER_LIST_END`` from ``enum rte_crypto_cipher_algorithm`` and
> + ``RTE_CRYPTO_AUTH_LIST_END`` from ``enum rte_crypto_auth_algorithm`` will be
> + removed.
> +
--
David Marchand
next prev parent reply other threads:[~2020-07-29 15:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 14:46 Arek Kusztal
2020-07-29 14:54 ` Kusztal, ArkadiuszX
2020-07-29 15:18 ` Bruce Richardson
2020-07-29 15:22 ` Trahe, Fiona
2020-07-29 15:24 ` David Marchand [this message]
2020-07-29 15:32 ` Trahe, Fiona
2020-07-31 9:38 ` Akhil Goyal
2020-08-06 16:09 ` Thomas Monjalon
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=CAJFAV8x0fHAA8zegMiuFN5pCKkNtxpWW-jzYq9Z35u-2oBtGhA@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=akhil.goyal@nxp.com \
--cc=anoobj@marvell.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=roy.fan.zhang@intel.com \
--cc=shallyv@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).