[dpdk-stable] patch 'doc: remove notice about AES-GCM IV and J0' has been queued to stable release 19.11.6

[luca.boccassi at gmail.com]

Hi,

FYI, your patch has been queued to stable release 19.11.6

Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet.
It will be pushed if I get no objections before 11/11/20. So please
shout if anyone has objections.

Also note that after the patch there's a diff of the upstream commit vs the
patch applied to the branch. This will indicate if there was any rebasing
needed to apply to the stable branch. If there were code changes for rebasing
(ie: not only metadata diffs), please double check that the rebase was
correctly done.

Queued patches are on a temporary branch at:
https://github.com/bluca/dpdk-stable

This queued commit can be viewed at:
https://github.com/bluca/dpdk-stable/commit/145749bc13de2fe2f7916b46f425b07fb42a7d5e

Thanks.

Luca Boccassi

---
>From 145749bc13de2fe2f7916b46f425b07fb42a7d5e Mon Sep 17 00:00:00 2001
From: Arek Kusztal <arkadiuszx.kusztal at intel.com>
Date: Wed, 14 Oct 2020 06:07:00 +0100
Subject: [PATCH] doc: remove notice about AES-GCM IV and J0

[ upstream commit 57e03d2a620534cee72a54396d799a0a6c1ca2d5 ]

This patch removes information about deprecation of AES-GCM/GMAC
API for IV without J0.

Fixes: fac52fb26a54 ("cryptodev: add option to support both IV and J0 for GCM")

Signed-off-by: Arek Kusztal <arkadiuszx.kusztal at 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 afa94b43e2..c2e1298342 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -67,12 +67,6 @@ Deprecation Notices
   In 19.11 PMDs will still update the field even when the offload is not
   enabled.
 
-* 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.
-
 * sched: To allow more traffic classes, flexible mapping of pipe queues to
   traffic classes, and subport level configuration of pipes and queues
   changes will be made to macros, data structures and API functions defined
-- 
2.27.0

---
  Diff of the applied patch vs upstream commit (please double-check if non-empty:
---
--- -	2020-11-09 18:40:11.859038676 +0000
+++ 0016-doc-remove-notice-about-AES-GCM-IV-and-J0.patch	2020-11-09 18:40:11.087310598 +0000
@@ -1 +1 @@
-From 57e03d2a620534cee72a54396d799a0a6c1ca2d5 Mon Sep 17 00:00:00 2001
+From 145749bc13de2fe2f7916b46f425b07fb42a7d5e Mon Sep 17 00:00:00 2001
@@ -5,0 +6,2 @@
+[ upstream commit 57e03d2a620534cee72a54396d799a0a6c1ca2d5 ]
+
@@ -10 +11,0 @@
-Cc: stable at dpdk.org
@@ -18 +19 @@
-index 22aecf0bab..43e0e09be5 100644
+index afa94b43e2..c2e1298342 100644
@@ -21,3 +22,3 @@
-@@ -132,12 +132,6 @@ Deprecation Notices
-   will be limited to maximum 256 queues.
-   Also compile time flag ``RTE_ETHDEV_QUEUE_STAT_CNTRS`` will be removed.
+@@ -67,12 +67,6 @@ Deprecation Notices
+   In 19.11 PMDs will still update the field even when the offload is not
+   enabled.