From: Stephen Hemminger <stephen@networkplumber.org>
To: Radu Nicolau <radu.nicolau@intel.com>
Cc: dev@dpdk.org, nkaithakadan@marvell.com, kai.ji@intel.com,
anoobj@marvell.com, Akhil Goyal <gakhil@marvell.com>,
Fan Zhang <fanzhang.oss@gmail.com>
Subject: Re: [PATCH v2 2/2] test/crypto: add tests for 256-NxA4/5/6 algorithms
Date: Mon, 19 Jan 2026 09:05:20 -0800 [thread overview]
Message-ID: <20260119090520.2442bf56@phoenix.local> (raw)
In-Reply-To: <20260119113000.2176714-2-radu.nicolau@intel.com>
On Mon, 19 Jan 2026 11:28:56 +0000
Radu Nicolau <radu.nicolau@intel.com> wrote:
> +struct nxa_256_test_data nea4_test_1 = {
> + .key = {
> + 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
> + 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
> + 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
> + 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
> + },
> + .iv = {
> + 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
> + 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
> + },
Could all these test vectors be declared static and const to avoid
any possibility of link mixups and corruption by crypto.
next prev parent reply other threads:[~2026-01-19 17:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 10:56 [PATCH 1/2] cryptodev: add support for 256-NxA4/5/6 algorithms Radu Nicolau
2026-01-07 10:56 ` [PATCH 2/2] test/crypto: add tests " Radu Nicolau
2026-01-19 8:12 ` [EXTERNAL] " Nithinsen Kaithakadan
2026-01-19 11:28 ` [PATCH v2 1/2] cryptodev: add support " Radu Nicolau
2026-01-19 11:28 ` [PATCH v2 2/2] test/crypto: add tests " Radu Nicolau
2026-01-19 17:05 ` Stephen Hemminger [this message]
2026-01-21 10:18 ` [PATCH v3 1/2] cryptodev: add support " Radu Nicolau
2026-01-21 10:18 ` [PATCH v3 2/2] test/crypto: add tests " Radu Nicolau
2026-01-21 15:15 ` [PATCH v4 1/2] cryptodev: add support " Radu Nicolau
2026-01-21 15:15 ` [PATCH v4 2/2] test/crypto: add tests " Radu Nicolau
2026-01-22 7:02 ` [EXTERNAL] " Nithinsen Kaithakadan
2026-01-22 10:25 ` [PATCH v5 1/2] cryptodev: add support " Radu Nicolau
2026-01-22 10:25 ` [PATCH v5 2/2] test/crypto: add tests " Radu Nicolau
2026-01-23 0:23 ` [PATCH v5 1/2] cryptodev: add support " Stephen Hemminger
2026-01-23 10:44 ` Radu Nicolau
2026-01-23 12:48 ` [PATCH v6 " Radu Nicolau
2026-01-23 12:48 ` [PATCH v6 2/2] test/crypto: add tests " Radu Nicolau
2026-01-29 4:29 ` [EXTERNAL] " Nithinsen Kaithakadan
2026-01-29 11:59 ` [PATCH v7 1/2] cryptodev: add support " Radu Nicolau
2026-01-29 11:59 ` [PATCH v7 2/2] test/crypto: add tests " Radu Nicolau
2026-01-30 11:12 ` [EXTERNAL] " Nithinsen Kaithakadan
2026-02-03 11:21 ` Radu Nicolau
2026-02-03 11:13 ` [PATCH v8 1/2] cryptodev: add support " Radu Nicolau
2026-02-03 11:13 ` [PATCH v8 2/2] test/crypto: add tests " Radu Nicolau
2026-02-03 14:00 ` [EXTERNAL] " Nithinsen Kaithakadan
2026-02-03 13:59 ` [EXTERNAL] [PATCH v8 1/2] cryptodev: add support " Nithinsen Kaithakadan
2026-02-06 19:48 ` 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=20260119090520.2442bf56@phoenix.local \
--to=stephen@networkplumber.org \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=gakhil@marvell.com \
--cc=kai.ji@intel.com \
--cc=nkaithakadan@marvell.com \
--cc=radu.nicolau@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