From: Akhil Goyal <akhil.goyal@nxp.com>
To: Arek Kusztal <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "fiona.trahe@intel.com" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: remove aes-gcm addition of j0 deprecation notice
Date: Fri, 9 Oct 2020 19:36:37 +0000 [thread overview]
Message-ID: <VI1PR04MB3168E0F78B956B2961DB8AEFE6080@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20201007085528.413-1-arkadiuszx.kusztal@intel.com>
Hi Arek,
> This patch removes information about deprecation of AES-GCM/GMAC
> API for IV without J0.
>
> Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> ---
> doc/guides/rel_notes/deprecation.rst | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst
> b/doc/guides/rel_notes/deprecation.rst
> index f9b72acb8..281f38048 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -235,12 +235,6 @@ Deprecation Notices
> ``RTE_CRYPTO_AUTH_LIST_END`` from ``enum rte_crypto_auth_algorithm``
> will be removed.
>
> -* cryptodev: support for using IV with all sizes is added, J0 still can
> - be used but only when IV length in following structs ``rte_crypto_auth_xform``,
> - ``rte_crypto_aead_xform`` is set to zero. When IV length is greater or equal
> - to one it means it represents IV, when is set to zero it means J0 is used
> - directly, in this case 16 bytes of J0 need to be passed.
> -
Could you please add a reference of the patch which implemented it in the description?
Regards,
Akhil
prev parent reply other threads:[~2020-10-09 19:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 8:55 Arek Kusztal
2020-10-09 19:36 ` 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=VI1PR04MB3168E0F78B956B2961DB8AEFE6080@VI1PR04MB3168.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@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).