From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: Owen Hilyard <ohilyard@iol.unh.edu>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "shall@iol.unh.edu" <shall@iol.unh.edu>,
"Ma, LihongX" <lihongx.ma@intel.com>,
"lylavoie@iol.unh.edu" <lylavoie@iol.unh.edu>,
"Chen, Zhaoyan" <zhaoyan.chen@intel.com>,
"Peng, Yuan" <yuan.peng@intel.com>
Subject: Re: [dts] [PATCH v2 1/7] rte flow: add test plan and test suite
Date: Tue, 27 Oct 2020 05:07:53 +0000 [thread overview]
Message-ID: <7099b560f3a8468580fc94e72304170e@intel.com> (raw)
In-Reply-To: <20201023232903.37387-1-ohilyard@iol.unh.edu>
> These are the base test plan and test suite files. Their function is heavily
> dependent on the following patches due to the runtime generation of test cases
> to avoid maintainability issues.
>
> Signed-off-by: Owen Hilyard <ohilyard@iol.unh.edu>
Applied the series, thanks
prev parent reply other threads:[~2020-10-27 5:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 20:50 [dts] [PATCH] rte flow: added test suite and framework Owen Hilyard
2020-10-14 21:02 ` [dts] [PATCH] rte flow: fixing checkpatch issues Owen Hilyard
2020-10-22 8:53 ` [dts] [PATCH] rte flow: added test suite and framework Tu, Lijuan
2020-10-23 18:18 ` Owen Hilyard
2020-10-23 23:28 ` [dts] [PATCH v2 1/7] rte flow: add test plan and test suite Owen Hilyard
2020-10-23 23:28 ` [dts] [PATCH v2 2/7] rte flow: add supporting data structures Owen Hilyard
2020-10-23 23:28 ` [dts] [PATCH v2 3/7] rte flow: Add base flow type Owen Hilyard
2020-10-23 23:28 ` [dts] [PATCH v2 4/7] rte flow: add more specifc data structures Owen Hilyard
2020-10-23 23:29 ` [dts] [PATCH v2 5/7] rte flow: add action items Owen Hilyard
2020-10-23 23:29 ` [dts] [PATCH v2 6/7] rte flow: add pattern items Owen Hilyard
2020-10-23 23:29 ` [dts] [PATCH v2 7/7] rte flow: add flow test generator Owen Hilyard
2020-10-23 23:29 ` [dts] [PATCH v2] " Owen Hilyard
2020-10-23 23:30 ` Owen Hilyard
2020-10-27 5:07 ` Tu, Lijuan [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=7099b560f3a8468580fc94e72304170e@intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=lihongx.ma@intel.com \
--cc=lylavoie@iol.unh.edu \
--cc=ohilyard@iol.unh.edu \
--cc=shall@iol.unh.edu \
--cc=yuan.peng@intel.com \
--cc=zhaoyan.chen@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).