From: Akhil Goyal <gakhil@marvell.com>
To: Ciara Power <ciara.power@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "kai.ji@intel.com" <kai.ji@intel.com>
Subject: RE: [EXT] [PATCH 3/3] app/test: add more cryptodev tests to meson suite
Date: Tue, 7 Mar 2023 17:23:05 +0000 [thread overview]
Message-ID: <CO6PR18MB448473CEB80C286A6257F9ECD8B79@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20230307171734.2872005-4-ciara.power@intel.com>
> Subject: [EXT] [PATCH 3/3] app/test: add more cryptodev tests to meson suite
>
> The meson driver-tests suite did not include some ipsec_mb SW Crypto
> PMD tests, and QAT tests. These are now added to avoid them being missed
> if the user runs tests only using the meson suite infrastructure.
>
> Signed-off-by: Ciara Power <ciara.power@intel.com>
> ---
This patch is ok for now, but it is not scalable.
We should look for a way to consolidate all cryptodev autotests under one name.
next prev parent reply other threads:[~2023-03-07 17:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 17:17 [PATCH 0/3] cryptodev test improvements Ciara Power
2023-03-07 17:17 ` [PATCH 1/3] test/crypto: fix skip condition for CPU crypto SGL Ciara Power
2023-03-07 17:43 ` Ji, Kai
2023-03-07 17:17 ` [PATCH 2/3] test/crypto: skip asym test if driver or device missing Ciara Power
2023-03-07 17:17 ` [PATCH 3/3] app/test: add more cryptodev tests to meson suite Ciara Power
2023-03-07 17:23 ` Akhil Goyal [this message]
2023-03-07 17:32 ` [EXT] " Power, Ciara
2023-03-07 17:42 ` Akhil Goyal
2023-03-07 17:43 ` [PATCH 0/3] cryptodev test improvements Ji, Kai
2023-03-16 18:16 ` Akhil Goyal
2023-03-07 17:46 ` Ji, Kai
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=CO6PR18MB448473CEB80C286A6257F9ECD8B79@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=kai.ji@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).