From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] doc: add cryptodev xform deprecation notice
Date: Mon, 1 Apr 2019 16:29:27 +0000 [thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B43589727429@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <20190322163431.28921-1-roy.fan.zhang@intel.com>
> -----Original Message-----
> From: Zhang, Roy Fan
> Sent: Friday, March 22, 2019 4:35 PM
> To: dev@dpdk.org
> Cc: akhil.goyal@nxp.com; Zhang, Roy Fan <roy.fan.zhang@intel.com>; Kusztal, ArkadiuszX
> <arkadiuszx.kusztal@intel.com>; De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Doherty,
> Declan <declan.doherty@intel.com>; Trahe, Fiona <fiona.trahe@intel.com>
> Subject: [PATCH v3] doc: add cryptodev xform deprecation notice
>
> 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>
Acked-by: Fiona Trahe <fiona.trahe@intel.com>
next prev parent reply other threads:[~2019-04-01 16:29 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
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 [this message]
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=348A99DA5F5B7549AA880327E580B43589727429@IRSMSX101.ger.corp.intel.com \
--to=fiona.trahe@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--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).