DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
	"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Trahe, Fiona" <fiona.trahe@intel.com>,
	Anoob Joseph <anoobj@marvell.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add cryptodev gcm iv deprecation notice
Date: Thu, 9 May 2019 09:03:30 +0000	[thread overview]
Message-ID: <VI1PR04MB48933783F682595EE5CC57B0E6330@VI1PR04MB4893.eurprd04.prod.outlook.com> (raw)
Message-ID: <20190509090330.5czFC87MyRi32kHjTO3zJ_AfvmvFoZbaFEXNEyhsTOU@z> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D897803C2825@irsmsx112.ger.corp.intel.com>



> -----Original Message-----
> From: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> Sent: Wednesday, May 8, 2019 1:53 PM
> To: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>; dev@dpdk.org
> Cc: Akhil Goyal <akhil.goyal@nxp.com>; Trahe, Fiona <fiona.trahe@intel.com>;
> Anoob Joseph <anoobj@marvell.com>
> Subject: RE: [PATCH] doc: add cryptodev gcm iv deprecation notice
> 
> 
> 
> > -----Original Message-----
> > From: Kusztal, ArkadiuszX
> > Sent: Wednesday, April 17, 2019 8:41 AM
> > To: dev@dpdk.org
> > Cc: akhil.goyal@nxp.com; Trahe, Fiona <fiona.trahe@intel.com>; De Lara
> > Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Kusztal, ArkadiuszX
> > <arkadiuszx.kusztal@intel.com>
> > Subject: [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: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> 
> Also, I am CC'ing Anoob, since he acked the patch that is actually making
> changes in the comments of the API,
> so I assume he agrees with this patch (needed for the other patch).

Acked-by: Akhil Goyal <akhil.goyal@nxp.com>

  parent reply	other threads:[~2019-05-09  9:03 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 [this message]
2019-05-09  9:03     ` Akhil Goyal
2019-05-09 11:31 ` Anoob Joseph
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=VI1PR04MB48933783F682595EE5CC57B0E6330@VI1PR04MB4893.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=anoobj@marvell.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).