From: Akhil Goyal <gakhil@marvell.com>
To: Kai Ji <kai.ji@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "pablo.de.lara.guarch@intel.com" <pablo.de.lara.guarch@intel.com>,
"adamx.dybkowski@intel.com" <adamx.dybkowski@intel.com>,
"damianx.nowak@intel.com" <damianx.nowak@intel.com>,
dpdk stable <stable@dpdk.org>
Subject: RE: [EXT] [dpdk-dev] [dpdk-dev v3] test/cryptodev: fix incomplete data length
Date: Thu, 11 Nov 2021 11:17:37 +0000 [thread overview]
Message-ID: <CO6PR18MB448407F2F337177C9D676D40D8949@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20211109104231.24280-1-kai.ji@intel.com>
> This patch fixes incorrect data lengths computation in cryptodev
> unit test. Previously some data lengths were incorrectly set, which
> was insensitive for crypto op unit tets but is critical for raw data
> path API unit tests. The patch addressed the issue by setting the
> correct data lengths for some tests.
>
> Fixes: 681f540da52b ("cryptodev: do not use AAD in wireless algorithms")
> Cc: pablo.de.lara.guarch@intel.com
>
> Fixes: e847fc512817 ("test/crypto: add encrypted digest case for AES-CTR-
> CMAC")
> Cc: adamx.dybkowski@intel.com
>
> Fixes: b1c1df46878d ("test/crypto: add ZUC test cases for auth-cipher")
> Cc: damianx.nowak@intel.com
>
> Signed-off-by: Kai Ji <kai.ji@intel.com>
> ---
Applied to dpdk-next-crypto
Cc: stable@dpdk.org
prev parent reply other threads:[~2021-11-11 11:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 15:42 [dpdk-dev] [dpdk-dev v1] " Kai Ji
2021-11-05 16:31 ` Zhang, Roy Fan
2021-11-08 4:05 ` [dpdk-dev] [EXT] " Anoob Joseph
2021-11-08 4:32 ` Anoob Joseph
2021-11-09 0:52 ` Ji, Kai
2021-11-09 10:27 ` [dpdk-dev] [dpdk-dev v2] " Kai Ji
2021-11-09 10:32 ` [dpdk-dev] [EXT] " Anoob Joseph
2021-11-09 10:42 ` [dpdk-dev] [dpdk-dev v3] " Kai Ji
2021-11-09 16:25 ` [dpdk-dev] [EXT] " Anoob Joseph
2021-11-11 11:17 ` Akhil Goyal [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=CO6PR18MB448407F2F337177C9D676D40D8949@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=adamx.dybkowski@intel.com \
--cc=damianx.nowak@intel.com \
--cc=dev@dpdk.org \
--cc=kai.ji@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=stable@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).