From: Ruifeng Wang <Ruifeng.Wang@arm.com>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>,
"declan.doherty@intel.com" <declan.doherty@intel.com>,
"ravi1.kumar@amd.com" <ravi1.kumar@amd.com>,
"anoobj@marvell.com" <anoobj@marvell.com>,
"roy.fan.zhang@intel.com" <roy.fan.zhang@intel.com>,
"fiona.trahe@intel.com" <fiona.trahe@intel.com>,
"tdu@semihalf.com" <tdu@semihalf.com>,
"rnagadheeraj@marvell.com" <rnagadheeraj@marvell.com>,
"adwivedi@marvell.com" <adwivedi@marvell.com>,
"g.singh@nxp.com" <g.singh@nxp.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"jianjay.zhou@huawei.com" <jianjay.zhou@huawei.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
Adam Dybkowski <adamx.dybkowski@intel.com>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH v2 4/4] test/crypto: do not check for PMD in tests
Date: Thu, 16 Apr 2020 15:28:40 +0000 [thread overview]
Message-ID: <HE1PR0801MB2025017740D880B3A8FF0B7E9ED80@HE1PR0801MB2025.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20200416092532.1922099-5-pablo.de.lara.guarch@intel.com>
> -----Original Message-----
> From: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> Sent: Thursday, April 16, 2020 5:26 PM
> To: declan.doherty@intel.com; ravi1.kumar@amd.com; Ruifeng Wang
> <Ruifeng.Wang@arm.com>; anoobj@marvell.com; roy.fan.zhang@intel.com;
> fiona.trahe@intel.com; tdu@semihalf.com; rnagadheeraj@marvell.com;
> adwivedi@marvell.com; g.singh@nxp.com; hemant.agrawal@nxp.com;
> jianjay.zhou@huawei.com
> Cc: dev@dpdk.org; Akhil.goyal@nxp.com; Pablo de Lara
> <pablo.de.lara.guarch@intel.com>; Adam Dybkowski
> <adamx.dybkowski@intel.com>
> Subject: [PATCH v2 4/4] test/crypto: do not check for PMD in tests
>
> Remove PMD bitmask, which selects the PMD to be tested
> for each test case. Instead, all PMDs are eligible
> to run all tests, and capability checking discards
> the PMDs which do not support each test case.
>
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> Acked-by: Adam Dybkowski <adamx.dybkowski@intel.com>
>
> ---
Tested-by: Ruifeng Wang <ruifeng.wang@arm.com>
next prev parent reply other threads:[~2020-04-16 15:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 18:04 [dpdk-dev] [PATCH 0/3] Crypto test refactoring (second phase) Pablo de Lara
2020-04-14 18:04 ` [dpdk-dev] [PATCH 1/3] cryptodev: add sessionless support feature flag Pablo de Lara
2020-04-15 10:38 ` Dybkowski, AdamX
2020-04-14 18:04 ` [dpdk-dev] [PATCH 2/3] test/crypto: check if device supports sessionless Pablo de Lara
2020-04-15 10:38 ` Dybkowski, AdamX
2020-04-14 18:04 ` [dpdk-dev] [PATCH 3/3] test/crypto: do not check for PMD in tests Pablo de Lara
2020-04-15 10:38 ` Dybkowski, AdamX
2020-04-16 8:28 ` [dpdk-dev] [PATCH 0/3] Crypto test refactoring (second phase) Ruifeng Wang
2020-04-16 13:28 ` De Lara Guarch, Pablo
2020-04-16 15:23 ` Ruifeng Wang
2020-04-16 9:25 ` [dpdk-dev] [PATCH v2 0/4] " Pablo de Lara
2020-04-16 9:25 ` [dpdk-dev] [PATCH v2 1/4] cryptodev: add sessionless support feature flag Pablo de Lara
2020-04-16 15:27 ` Ruifeng Wang
2020-04-16 9:25 ` [dpdk-dev] [PATCH v2 2/4] test/crypto: check if device supports sessionless Pablo de Lara
2020-04-16 15:27 ` Ruifeng Wang
2020-04-16 9:25 ` [dpdk-dev] [PATCH v2 3/4] test/crypto: check if device supports out-of-place ops Pablo de Lara
2020-04-16 13:41 ` Dybkowski, AdamX
2020-04-16 15:28 ` Ruifeng Wang
2020-04-16 9:25 ` [dpdk-dev] [PATCH v2 4/4] test/crypto: do not check for PMD in tests Pablo de Lara
2020-04-16 15:28 ` Ruifeng Wang [this message]
2020-04-16 16:52 ` [dpdk-dev] [PATCH v2 0/4] Crypto test refactoring (second phase) Trahe, Fiona
2020-04-19 21:13 ` 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=HE1PR0801MB2025017740D880B3A8FF0B7E9ED80@HE1PR0801MB2025.eurprd08.prod.outlook.com \
--to=ruifeng.wang@arm.com \
--cc=adamx.dybkowski@intel.com \
--cc=adwivedi@marvell.com \
--cc=akhil.goyal@nxp.com \
--cc=anoobj@marvell.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=g.singh@nxp.com \
--cc=hemant.agrawal@nxp.com \
--cc=jianjay.zhou@huawei.com \
--cc=nd@arm.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=ravi1.kumar@amd.com \
--cc=rnagadheeraj@marvell.com \
--cc=roy.fan.zhang@intel.com \
--cc=tdu@semihalf.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).