From: Luca Vizzarro <Luca.Vizzarro@arm.com>
To: Andrew Bailey <abailey@iol.unh.edu>,
dev@dpdk.org, patrickrobb1997@gmail.com, dladd@iol.unh.edu
Cc: knimoji@iol.unh.edu, lylavoie@iol.unh.edu
Subject: Re: [PATCH v4 1/3] dts: add directory for test resources
Date: Tue, 20 Oct 2026 13:11:31 +0100 [thread overview]
Message-ID: <241b21b0-9cff-43d4-98dd-14e8dc5fffa1@arm.com> (raw)
In-Reply-To: <20261019202252.907692-1-abailey@iol.unh.edu>
On 19/10/2026 21:22, Andrew Bailey wrote:
> The crypto verify test suite being added in this series requires an
> input vector file. The two vector files added in this commit are
> relocated from old DTS to new DTS. This will allow the crypto verify
> test suite to access the required vector files for verify testing.
Hi Andrew, this patch is fine. The commit description isn't, once this
patch is merged there is no concept of patch series, so the description
should be able to describe what it's doing on its own.
>
> Signed-off-by: Andrew Bailey <abailey@iol.unh.edu>
prev parent reply other threads:[~2026-10-20 12:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 19:35 [RFC] dts: add verify coverage for cryptodev testing Andrew Bailey
2026-05-14 17:25 ` [PATCH v1 1/3] dts: add directory for test resources Andrew Bailey
2026-05-14 17:25 ` [PATCH v1 2/3] dts: fix cryptodev verify parsing Andrew Bailey
2026-05-14 17:25 ` [PATCH v1 3/3] dts: add verify coverage for cryptodev testing Andrew Bailey
2026-07-06 13:34 ` [PATCH v2 1/3] dts: add directory for test resources Andrew Bailey
2026-07-06 13:34 ` [PATCH v2 2/3] dts: fix cryptodev verify parsing Andrew Bailey
2026-07-06 13:34 ` [PATCH v2 3/3] dts: add verify coverage for cryptodev testing Andrew Bailey
2026-07-06 15:02 ` [PATCH v3 1/3] dts: add directory for test resources Andrew Bailey
2026-07-06 15:02 ` [PATCH v3 2/3] dts: fix cryptodev verify parsing Andrew Bailey
2026-07-06 15:02 ` [PATCH v3 3/3] dts: add verify coverage for cryptodev testing Andrew Bailey
2026-10-19 20:22 ` [PATCH v4 1/3] dts: add directory for test resources Andrew Bailey
2026-10-19 20:22 ` [PATCH v4 2/3] dts: fix cryptodev verify parsing Andrew Bailey
2026-10-20 12:12 ` Luca Vizzarro
2026-10-19 20:22 ` [PATCH v4 3/3] dts: add verify coverage for cryptodev testing Andrew Bailey
2026-10-20 16:47 ` Luca Vizzarro
2026-10-20 12:11 ` Luca Vizzarro [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=241b21b0-9cff-43d4-98dd-14e8dc5fffa1@arm.com \
--to=luca.vizzarro@arm.com \
--cc=abailey@iol.unh.edu \
--cc=dev@dpdk.org \
--cc=dladd@iol.unh.edu \
--cc=knimoji@iol.unh.edu \
--cc=lylavoie@iol.unh.edu \
--cc=patrickrobb1997@gmail.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