From: Vikash Poddar <vikash.chandrax.poddar@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Akhil Goyal <gakhil@marvell.com>,
Fan Zhang <fanzhang.oss@gmail.com>
Cc: dev@dpdk.org, Vikash Poddar <vikash.chandrax.poddar@intel.com>,
shirik@nvidia.com
Subject: [PATCH] test/crypto: fix typo in AES test
Date: Mon, 30 Jan 2023 12:03:03 +0000 [thread overview]
Message-ID: <20230130120303.793537-1-vikash.chandrax.poddar@intel.com> (raw)
Fix the spelling of scater to scatter in cryptodev AES test vector
header file
Fixes: 2692b02e03b2 ("test/crypto: add multi-segment out-of-place AES-XTS")
Cc: shirik@nvidia.com
Signed-off-by: Vikash Poddar <vikash.chandrax.poddar@intel.com>
---
.mailmap | 1 +
app/test/test_cryptodev_aes_test_vectors.h | 16 ++++++++--------
2 files changed, 9 insertions(+), 8 deletions(-)
diff --git a/.mailmap b/.mailmap
index 75884b6fe2..c6650e32f6 100644
--- a/.mailmap
+++ b/.mailmap
@@ -1386,6 +1386,7 @@ Vijay Kumar Srivastava <vsrivast@xilinx.com>
Vijay Srivastava <vijays@solarflare.com>
Vikas Aggarwal <vikas.aggarwal@caviumnetworks.com>
Vikas Gupta <vikas.gupta@broadcom.com>
+Vikash Poddar <vikash.chandrax.poddar@intel.com>
Vimal Chungath <vcchunga@amazon.com>
Vincent Guo <guopengfei160@163.com>
Vincent Jardin <vincent.jardin@6wind.com>
diff --git a/app/test/test_cryptodev_aes_test_vectors.h b/app/test/test_cryptodev_aes_test_vectors.h
index ea7b21ce53..f3686beeb5 100644
--- a/app/test/test_cryptodev_aes_test_vectors.h
+++ b/app/test/test_cryptodev_aes_test_vectors.h
@@ -4969,7 +4969,7 @@ static const struct blockcipher_test_case aes_cipheronly_test_cases[] = {
},
{
.test_descr = "AES-256-XTS Encryption (512-byte plaintext"
- " Dataunit 512) Scater gather OOP",
+ " Dataunit 512) Scatter gather OOP",
.test_data = &aes_test_data_xts_wrapped_key_48_pt_512_du_512,
.op_mask = BLOCKCIPHER_TEST_OP_ENCRYPT,
.feature_mask = BLOCKCIPHER_TEST_FEATURE_OOP |
@@ -4979,7 +4979,7 @@ static const struct blockcipher_test_case aes_cipheronly_test_cases[] = {
},
{
.test_descr = "AES-256-XTS Decryption (512-byte plaintext"
- " Dataunit 512) Scater gather OOP",
+ " Dataunit 512) Scatter gather OOP",
.test_data = &aes_test_data_xts_wrapped_key_48_pt_512_du_512,
.op_mask = BLOCKCIPHER_TEST_OP_DECRYPT,
.feature_mask = BLOCKCIPHER_TEST_FEATURE_OOP |
@@ -4989,7 +4989,7 @@ static const struct blockcipher_test_case aes_cipheronly_test_cases[] = {
},
{
.test_descr = "AES-256-XTS Encryption (512-byte plaintext"
- " Dataunit 0) Scater gather OOP",
+ " Dataunit 0) Scatter gather OOP",
.test_data = &aes_test_data_xts_wrapped_key_48_pt_512_du_0,
.op_mask = BLOCKCIPHER_TEST_OP_ENCRYPT,
.feature_mask = BLOCKCIPHER_TEST_FEATURE_OOP |
@@ -4999,7 +4999,7 @@ static const struct blockcipher_test_case aes_cipheronly_test_cases[] = {
},
{
.test_descr = "AES-256-XTS Decryption (512-byte plaintext"
- " Dataunit 0) Scater gather OOP",
+ " Dataunit 0) Scatter gather OOP",
.test_data = &aes_test_data_xts_wrapped_key_48_pt_512_du_0,
.op_mask = BLOCKCIPHER_TEST_OP_DECRYPT,
.feature_mask = BLOCKCIPHER_TEST_FEATURE_OOP |
@@ -5009,7 +5009,7 @@ static const struct blockcipher_test_case aes_cipheronly_test_cases[] = {
},
{
.test_descr = "AES-256-XTS Encryption (4096-byte plaintext"
- " Dataunit 4096) Scater gather OOP",
+ " Dataunit 4096) Scatter gather OOP",
.test_data = &aes_test_data_xts_wrapped_key_48_pt_4096_du_4096,
.op_mask = BLOCKCIPHER_TEST_OP_ENCRYPT,
.feature_mask = BLOCKCIPHER_TEST_FEATURE_OOP |
@@ -5019,7 +5019,7 @@ static const struct blockcipher_test_case aes_cipheronly_test_cases[] = {
},
{
.test_descr = "AES-256-XTS Decryption (4096-byte plaintext"
- " Dataunit 4096) Scater gather OOP",
+ " Dataunit 4096) Scatter gather OOP",
.test_data = &aes_test_data_xts_wrapped_key_48_pt_4096_du_4096,
.op_mask = BLOCKCIPHER_TEST_OP_DECRYPT,
.feature_mask = BLOCKCIPHER_TEST_FEATURE_OOP |
@@ -5029,7 +5029,7 @@ static const struct blockcipher_test_case aes_cipheronly_test_cases[] = {
},
{
.test_descr = "AES-256-XTS Encryption (4096-byte plaintext"
- " Dataunit 0) Scater gather OOP",
+ " Dataunit 0) Scatter gather OOP",
.test_data = &aes_test_data_xts_wrapped_key_48_pt_4096_du_0,
.op_mask = BLOCKCIPHER_TEST_OP_ENCRYPT,
.feature_mask = BLOCKCIPHER_TEST_FEATURE_OOP |
@@ -5039,7 +5039,7 @@ static const struct blockcipher_test_case aes_cipheronly_test_cases[] = {
},
{
.test_descr = "AES-256-XTS Decryption (4096-byte plaintext"
- " Dataunit 0) Scater gather OOP",
+ " Dataunit 0) Scatter gather OOP",
.test_data = &aes_test_data_xts_wrapped_key_48_pt_4096_du_0,
.op_mask = BLOCKCIPHER_TEST_OP_DECRYPT,
.feature_mask = BLOCKCIPHER_TEST_FEATURE_OOP |
--
2.25.1
--------------------------------------------------------------
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.
next reply other threads:[~2023-01-30 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 12:03 Vikash Poddar [this message]
2023-01-30 14:27 ` Ji, Kai
2023-02-01 14:08 ` 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=20230130120303.793537-1-vikash.chandrax.poddar@intel.com \
--to=vikash.chandrax.poddar@intel.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=gakhil@marvell.com \
--cc=shirik@nvidia.com \
--cc=thomas@monjalon.net \
/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).