From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: stable@dpdk.org, dev@dpdk.org, shreyansh.jain@nxp.com
Subject: Re: [dpdk-stable] [PATCH v2 2/4] app/test: add missing rawdev test to meson build
Date: Mon, 01 Jul 2019 20:10:18 +0200 [thread overview]
Message-ID: <1850000.GSOBcrzYNF@xps> (raw)
In-Reply-To: <20190621155659.29297-3-bruce.richardson@intel.com>
21/06/2019 17:56, Bruce Richardson:
> the test_rawdev.c file was missing from the meson.build file, and the test
> case from the list of test commands.
>
> Fixes: 55ca1b0f2151 ("raw/skeleton: add test cases")
> Cc: shreyansh.jain@nxp.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
> @@ -179,6 +181,7 @@ fast_parallel_test_names = [
> 'multiprocess_autotest',
> 'per_lcore_autotest',
> 'prefetch_autotest',
> + 'rawdev_autotest',
> 'rcu_qsbr_autotest',
> 'red_autotest',
> 'ring_autotest',
For consistency, I think rawdev_autotest should go in driver_test_names,
as it is testing the skeleton driver.
next prev parent reply other threads:[~2019-07-01 18:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190619170802.7691-1-bruce.richardson@intel.com>
2019-06-19 17:08 ` [dpdk-stable] [PATCH 1/2] raw/skeleton: fix failing test case Bruce Richardson
2019-06-19 17:08 ` [dpdk-stable] [PATCH 2/2] app/test: add missing rawdev autotest to meson build Bruce Richardson
[not found] ` <20190621155659.29297-1-bruce.richardson@intel.com>
2019-06-21 15:56 ` [dpdk-stable] [PATCH v2 1/4] raw/skeleton: fix failing test case Bruce Richardson
2019-06-27 11:50 ` [dpdk-stable] [dpdk-dev] " Hemant Agrawal
2019-07-01 18:03 ` [dpdk-stable] " Thomas Monjalon
2019-06-21 15:56 ` [dpdk-stable] [PATCH v2 2/4] app/test: add missing rawdev test to meson build Bruce Richardson
2019-07-01 18:10 ` Thomas Monjalon [this message]
[not found] ` <20190702095608.20722-1-bruce.richardson@intel.com>
2019-07-02 9:56 ` [dpdk-stable] [PATCH v3 1/3] app/test: add missing rawdev autotest " Bruce Richardson
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=1850000.GSOBcrzYNF@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=shreyansh.jain@nxp.com \
--cc=stable@dpdk.org \
/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).