diff mbox series

[v2] doc: remove aes-gcm addition of j0 deprecation notice

Message ID 20201014050700.863-1-arkadiuszx.kusztal@intel.com (mailing list archive)
State Accepted, archived
Delegated to: akhil goyal
Headers
Series [v2] doc: remove aes-gcm addition of j0 deprecation notice |

Checks

Context Check Description
ci/checkpatch warning coding style issues
ci/travis-robot success Travis build: passed
ci/Intel-compilation success Compilation OK

Commit Message

Arkadiusz Kusztal Oct. 14, 2020, 5:07 a.m. UTC 
  This patch removes information about deprecation of AES-GCM/GMAC
API for IV without J0.

J0 was added with the following patch:
- cryptodev: add an option to support both iv and J0 for GCM [1]
[1] (http://patchwork.dpdk.org/patch/52886/)

Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
---
v2:
- added reference to the patch in question

 doc/guides/rel_notes/deprecation.rst | 6 ------
 1 file changed, 6 deletions(-)

Comments

Akhil Goyal Oct. 28, 2020, 11:14 a.m. UTC | #1 
> This patch removes information about deprecation of AES-GCM/GMAC
> API for IV without J0.
> 
> J0 was added with the following patch:
> - cryptodev: add an option to support both iv and J0 for GCM [1]
> [1]
> (http://patchwork.dpdk.org/patch/52886/)
> 
> Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> ---
Fixes: fac52fb26a54 ("cryptodev: add option to support both IV and J0 for GCM")
    Cc: stable@dpdk.org

Added and applied to dpdk-next-crypto
diff mbox series

Patch

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.
-
 * scheduler: The functions ``rte_cryptodev_scheduler_slave_attach``,
   ``rte_cryptodev_scheduler_slave_detach`` and
   ``rte_cryptodev_scheduler_slaves_get`` will be replaced in 20.11 by