From: Akhil Goyal <akhil.goyal@nxp.com>
To: Tejasree Kondoj <ktejasree@marvell.com>,
Radu Nicolau <radu.nicolau@intel.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>,
Fan Zhang <roy.fan.zhang@intel.com>
Cc: Anoob Joseph <anoobj@marvell.com>,
Ankur Dwivedi <adwivedi@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 2/2] test/crypto: support SSL/TLS way of cipher-auth operations
Date: Tue, 19 Jan 2021 17:00:59 +0000 [thread overview]
Message-ID: <VI1SPR01MB03631BA4837A84EB7A22B6FDE6A30@VI1SPR01MB0363.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20201218141016.1834-3-ktejasree@marvell.com>
Hi Tejasree,
> Subject: [PATCH 2/2] test/crypto: support SSL/TLS way of cipher-auth operations
>
> Adding support for SSL/TLS way of cipher-auth operations order
> - auth generation followed by encryption
> - decryption followed by auth verify
>
> Signed-off-by: Tejasree Kondoj <ktejasree@marvell.com>
> ---
With this patch the following existing case is failing on NXP platforms. Please check.
10) TestCase AES-128-CBC HMAC-SHA1 Encryption Digest Scatter Gather line 634 FAILED: Generated digest data not as expected
Fiona/Fan,
Could you please check this patch on intel platform?
Regards,
Akhil
next prev parent reply other threads:[~2021-01-19 17:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 14:10 [dpdk-dev] [PATCH 0/2] " Tejasree Kondoj
2020-12-18 14:10 ` [dpdk-dev] [PATCH 1/2] common/cpt: " Tejasree Kondoj
2020-12-18 14:10 ` [dpdk-dev] [PATCH 2/2] test/crypto: " Tejasree Kondoj
2021-01-19 17:00 ` Akhil Goyal [this message]
2021-01-19 18:02 ` Doherty, Declan
2021-01-20 12:51 ` Zhang, Roy Fan
2021-01-20 14:34 ` Zhang, Roy Fan
2021-01-20 14:40 ` Tejasree Kondoj
2021-01-21 9:26 ` Kusztal, ArkadiuszX
2021-01-21 10:02 ` Tejasree Kondoj
2021-01-15 5:31 ` [dpdk-dev] [PATCH 0/2] " Anoob Joseph
2021-01-21 7:26 ` Tejasree Kondoj
2021-01-25 16:56 ` Akhil Goyal
2021-01-27 12:00 ` Tejasree Kondoj
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=VI1SPR01MB03631BA4837A84EB7A22B6FDE6A30@VI1SPR01MB0363.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=adwivedi@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=ktejasree@marvell.com \
--cc=radu.nicolau@intel.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).