From: "Ji, Kai" <kai.ji@intel.com>
To: "Sivaramakrishnan, VenkatX" <venkatx.sivaramakrishnan@intel.com>,
"Akhil Goyal" <gakhil@marvell.com>,
Fan Zhang <fanzhang.oss@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [PATCH 2/2] test/crypto: add negative test cases for cipher buffer alignment
Date: Mon, 6 Nov 2023 23:25:15 +0000 [thread overview]
Message-ID: <SN6PR11MB3408D571ABCD59DD8D047F6181AAA@SN6PR11MB3408.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20231103133037.782512-2-venkatx.sivaramakrishnan@intel.com>
[-- Attachment #1: Type: text/plain, Size: 657 bytes --]
Acked-by: Kai Ji <kai.ji@intel.com>
________________________________
From: Sivaramakrishnan Venkat <venkatx.sivaramakrishnan@intel.com>
Sent: 03 November 2023 13:30
To: Akhil Goyal <gakhil@marvell.com>; Fan Zhang <fanzhang.oss@gmail.com>
Cc: dev@dpdk.org <dev@dpdk.org>; stable@dpdk.org <stable@dpdk.org>; Sivaramakrishnan, VenkatX <venkatx.sivaramakrishnan@intel.com>
Subject: [PATCH 2/2] test/crypto: add negative test cases for cipher buffer alignment
add negative test cases for 3DES CBC and AES CBC
cipher algorithms for buffer misalignment
Signed-off-by: Sivaramakrishnan Venkat <venkatx.sivaramakrishnan@intel.com>
---
--
2.25.1
[-- Attachment #2: Type: text/html, Size: 1548 bytes --]
next prev parent reply other threads:[~2023-11-06 23:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 13:30 [PATCH 1/2] crypto/qat: fix block cipher misalignment for AES CBC and 3DES CBC Sivaramakrishnan Venkat
2023-11-03 13:30 ` [PATCH 2/2] test/crypto: add negative test cases for cipher buffer alignment Sivaramakrishnan Venkat
2023-11-06 23:25 ` Ji, Kai [this message]
2023-11-13 7:00 ` [EXT] " Akhil Goyal
2023-11-17 9:38 ` Sivaramakrishnan, VenkatX
2023-11-06 23:24 ` [PATCH 1/2] crypto/qat: fix block cipher misalignment for AES CBC and 3DES CBC Ji, Kai
2023-11-17 12:37 ` [PATCH v2] " Sivaramakrishnan Venkat
2023-11-17 14:43 ` Power, Ciara
2023-11-22 16:23 ` Thomas Monjalon
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=SN6PR11MB3408D571ABCD59DD8D047F6181AAA@SN6PR11MB3408.namprd11.prod.outlook.com \
--to=kai.ji@intel.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=gakhil@marvell.com \
--cc=stable@dpdk.org \
--cc=venkatx.sivaramakrishnan@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).