From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: Akhil Goyal <akhil.goyal@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"Dybkowski, AdamX" <adamx.dybkowski@intel.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH] cryptodev: clarify wireless inputs in digest-encrypted cases
Date: Tue, 22 Oct 2019 12:32:23 +0000 [thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B435A217B76E@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <VE1PR04MB6639E1C75A1F06DBAA0E2BF4E6680@VE1PR04MB6639.eurprd04.prod.outlook.com>
> -----Original Message-----
> From: Akhil Goyal [mailto:akhil.goyal@nxp.com]
> Sent: Tuesday, October 22, 2019 1:08 PM
> To: Trahe, Fiona <fiona.trahe@intel.com>; dev@dpdk.org
> Cc: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>; Dybkowski, AdamX
> <adamx.dybkowski@intel.com>
> Subject: RE: [PATCH] cryptodev: clarify wireless inputs in digest-encrypted cases
>
>
>
> @@ -590,7 +590,9 @@ struct rte_crypto_sym_op {
> * For SNOW 3G @ RTE_CRYPTO_CIPHER_SNOW3G_UEA2,
> * KASUMI @ RTE_CRYPTO_CIPHER_KASUMI_F8
> * and ZUC @ RTE_CRYPTO_CIPHER_ZUC_EEA3,
> - * this field should be in bits.
> + * this field should be in bits and must be
> + * 8-bit multiples in cases of encrypted
> + * digest.
> */
>
> Same change may be done in other 3 fields.
Ok, thanks, I'll send v2
next prev parent reply other threads:[~2019-10-22 12:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 11:34 Fiona Trahe
2019-10-22 11:48 ` Akhil Goyal
2019-10-22 12:00 ` Trahe, Fiona
2019-10-22 12:08 ` Akhil Goyal
2019-10-22 12:32 ` Trahe, Fiona [this message]
2019-10-22 13:20 ` [dpdk-dev] [PATCH v2] " Fiona Trahe
2019-10-22 13:24 ` Akhil Goyal
2019-10-22 14:46 ` Trahe, Fiona
2019-10-23 14:59 ` Akhil Goyal
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=348A99DA5F5B7549AA880327E580B435A217B76E@IRSMSX101.ger.corp.intel.com \
--to=fiona.trahe@intel.com \
--cc=adamx.dybkowski@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
/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).