From: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
To: Akhil Goyal <akhil.goyal@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "anoobj@marvell.com" <anoobj@marvell.com>,
"Doherty, Declan" <declan.doherty@intel.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>,
"asomalap@amd.com" <asomalap@amd.com>,
"rnagadheeraj@marvell.com" <rnagadheeraj@marvell.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce move of aes gmac algorithm to aead
Date: Wed, 5 Aug 2020 14:54:02 +0000 [thread overview]
Message-ID: <CY4PR11MB1830E12198D4DCBF44F232EF9F4B0@CY4PR11MB1830.namprd11.prod.outlook.com> (raw)
In-Reply-To: <VI1PR04MB31682E12EDCC3ABB67BF6A62E64B0@VI1PR04MB3168.eurprd04.prod.outlook.com>
I will send v2 soon then.
-----Original Message-----
From: Akhil Goyal <akhil.goyal@nxp.com>
Sent: środa, 5 sierpnia 2020 16:40
To: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>; dev@dpdk.org
Cc: anoobj@marvell.com; Doherty, Declan <declan.doherty@intel.com>; Trahe, Fiona <fiona.trahe@intel.com>; asomalap@amd.com; rnagadheeraj@marvell.com; Hemant Agrawal <hemant.agrawal@nxp.com>; De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Zhang, Roy Fan <roy.fan.zhang@intel.com>
Subject: RE: [PATCH] doc: announce move of aes gmac algorithm to aead
> Subject: RE: [PATCH] doc: announce move of aes gmac algorithm to aead
>
> > This patch announces removal of RTE_CRYPTO_AUTH_AES_GMAC from
> > rte_crypto_auth_algorithm and addition of RTE_CRYPTO_AEAD_AES_GMAC
> > to rte_crypto_aead_algorithm.
> >
You should probably explain the reason of this migration in the description.
> > Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> > ---
> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
prev parent reply other threads:[~2020-08-05 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 14:24 Arek Kusztal
2020-08-05 14:36 ` Akhil Goyal
2020-08-05 14:39 ` Akhil Goyal
2020-08-05 14:54 ` Kusztal, ArkadiuszX [this message]
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=CY4PR11MB1830E12198D4DCBF44F232EF9F4B0@CY4PR11MB1830.namprd11.prod.outlook.com \
--to=arkadiuszx.kusztal@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=anoobj@marvell.com \
--cc=asomalap@amd.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=rnagadheeraj@marvell.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).