DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
Cc: dev@dpdk.org, "Trahe, Fiona" <fiona.trahe@intel.com>,
	"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
	"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
	Anoob Joseph <anoobj@marvell.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add cryptodev gcm iv deprecation notice
Date: Mon, 13 May 2019 23:25:45 +0200	[thread overview]
Message-ID: <1801852.dfV3BK6j5X@xps> (raw)
Message-ID: <20190513212545.pDK2Dr4owNFz7ZN0Wqd6wbr8Rkhf6O3l51MbbgY0zco@z> (raw)
In-Reply-To: <348A99DA5F5B7549AA880327E580B43589743C1B@IRSMSX101.ger.corp.intel.com>

> > 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.
> [Fiona] nit - I would say "With this change..." rather than "Right now..."
> Apart from this
> Acked-by: Fiona Trahe <fiona.trahe@intel.com>

Updated and applied, thanks

> > Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
Acked-by: Anoob Joseph <anoobj@marvell.com>



  parent reply	other threads:[~2019-05-13 21:25 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 [this message]
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
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=1801852.dfV3BK6j5X@xps \
    --to=thomas@monjalon.net \
    --cc=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).