From: Anoob Joseph <anoobj@marvell.com>
To: Arek Kusztal <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"fiona.trahe@intel.com" <fiona.trahe@intel.com>,
"pablo.de.lara.guarch@intel.com" <pablo.de.lara.guarch@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add cryptodev gcm iv deprecation notice
Date: Thu, 9 May 2019 11:31:56 +0000 [thread overview]
Message-ID: <MN2PR18MB2877BD499D1C7749FF08CB2ADF330@MN2PR18MB2877.namprd18.prod.outlook.com> (raw)
Message-ID: <20190509113156.LMRUwqUDApLsVjNiwoi2_pxX3LysIUZqrVpv4bNjA6o@z> (raw)
In-Reply-To: <20190417074113.10896-1-arkadiuszx.kusztal@intel.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Arek Kusztal
> Sent: Wednesday, April 17, 2019 1:11 PM
> To: dev@dpdk.org
> Cc: akhil.goyal@nxp.com; fiona.trahe@intel.com;
> pablo.de.lara.guarch@intel.com; Arek Kusztal
> <arkadiuszx.kusztal@intel.com>
> Subject: [dpdk-dev] [PATCH] doc: add cryptodev gcm iv deprecation notice
>
> This patch adds deprecation notice of changing iv behaviour when using
> Galois Counter Mode of operation. Right now IV of all supported sizes can be
> used.
>
> Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Acked-by: Anoob Joseph <anoobj@marvell.com>
next prev parent reply other threads:[~2019-05-09 11:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 7:41 Arek Kusztal
2019-04-17 7:41 ` Arek Kusztal
2019-04-17 11:32 ` Trahe, Fiona
2019-04-17 11:32 ` Trahe, Fiona
2019-05-13 21:25 ` Thomas Monjalon
2019-05-13 21:25 ` Thomas Monjalon
2019-05-08 8:23 ` De Lara Guarch, Pablo
2019-05-08 8:23 ` De Lara Guarch, Pablo
2019-05-09 9:03 ` Akhil Goyal
2019-05-09 9:03 ` Akhil Goyal
2019-05-09 11:31 ` Anoob Joseph [this message]
2019-05-09 11:31 ` Anoob Joseph
2019-04-30 6:59 Akhil Goyal
2019-04-30 6:59 ` Akhil Goyal
2019-05-03 18:09 ` Trahe, Fiona
2019-05-03 18:09 ` Trahe, Fiona
2019-05-04 18:06 ` Liron Himi
2019-05-04 18:06 ` Liron Himi
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=MN2PR18MB2877BD499D1C7749FF08CB2ADF330@MN2PR18MB2877.namprd18.prod.outlook.com \
--to=anoobj@marvell.com \
--cc=akhil.goyal@nxp.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=pablo.de.lara.guarch@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).