From: Akhil Goyal <akhil.goyal@nxp.com>
To: Fan Zhang <roy.fan.zhang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "arkadiuszx.kusztal@intel.com" <arkadiuszx.kusztal@intel.com>,
"pablo.de.lara.guarch@intel.com" <pablo.de.lara.guarch@intel.com>,
"declan.doherty@intel.com" <declan.doherty@intel.com>,
"fiona.trahe@intel.com" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] doc: add cryptodev xform deprecation notice
Date: Fri, 29 Mar 2019 13:59:35 +0000 [thread overview]
Message-ID: <d36f8ab2-566a-bb56-f2e0-53eef78c1703@nxp.com> (raw)
Message-ID: <20190329135935.xKLG3J76FAS4PonGMjKD_V9KfHrWAmzEflLdd5qvi6o@z> (raw)
In-Reply-To: <20190322163431.28921-1-roy.fan.zhang@intel.com>
On 3/22/2019 10:04 PM, Fan Zhang wrote:
> This patch adds the deprecation notice of changing Cryptodev
> symmetric xform structure. The proposed change is to making
> key pointers in the crypto xforms (cipher, auth, aead) to
> indicate neither the library or the drivers will not change
> the content of the key buffer.
>
> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> ---
> v3:
> - Removed target release.
>
> v2:
> - Added description.
>
> doc/guides/rel_notes/deprecation.rst | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index 1b4fcb7e6..f35ac5b96 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -75,3 +75,7 @@ Deprecation Notices
>
> * crypto/aesni_mb: the minimum supported intel-ipsec-mb library version will be
> changed from 0.49.0 to 0.52.0.
> +
> +* cryptodev: the ``uint8_t *data`` member of ``key`` structure in the xforms
> + structure (``rte_crypto_cipher_xform``, ``rte_crypto_auth_xform``, and
> + ``rte_crypto_aead_xform``) will be changed to ``const uint8_t *data``.
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
next prev parent reply other threads:[~2019-03-29 13:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 11:17 [dpdk-dev] [PATCH] " Fan Zhang
2019-02-28 10:08 ` Akhil Goyal
2019-02-28 11:27 ` Zhang, Roy Fan
2019-03-01 10:46 ` [dpdk-dev] [PATCH v2] " Fan Zhang
2019-03-22 16:34 ` [dpdk-dev] [PATCH v3] " Fan Zhang
2019-03-22 16:34 ` Fan Zhang
2019-03-29 13:59 ` Akhil Goyal [this message]
2019-03-29 13:59 ` Akhil Goyal
2019-03-29 14:15 ` Akhil Goyal
2019-03-29 14:15 ` Akhil Goyal
2019-03-29 15:49 ` Akhil Goyal
2019-03-29 15:49 ` Akhil Goyal
2019-03-29 15:59 ` Akhil Goyal
2019-03-29 15:59 ` Akhil Goyal
2019-03-29 19:56 ` Thomas Monjalon
2019-03-29 19:56 ` Thomas Monjalon
2019-04-01 16:29 ` Trahe, Fiona
2019-04-01 16:29 ` Trahe, Fiona
2019-04-03 9:11 ` Anoob Joseph
2019-04-03 9:11 ` Anoob Joseph
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=d36f8ab2-566a-bb56-f2e0-53eef78c1703@nxp.com \
--to=akhil.goyal@nxp.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=roy.fan.zhang@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).