From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Mo, YufengX" <yufengx.mo@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Mo, YufengX" <yufengx.mo@intel.com>
Subject: Re: [dts] [PATCH V5 0/2] [examples/flow_classify]: upload test plan
Date: Wed, 26 Jun 2019 08:10:30 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BAC51E1@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1561450799-144563-1-git-send-email-yufengx.mo@intel.com>
Applied the series, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of yufengmx
> Sent: Tuesday, June 25, 2019 4:20 PM
> To: dts@dpdk.org
> Cc: Mo, YufengX <yufengx.mo@intel.com>
> Subject: [dts] [PATCH V5 0/2] [examples/flow_classify]: upload test plan
>
> upload examples/flow_classify test plan update test plan index list
>
> v5:
> - Follow Tu, Lijuan suggestion
> - fix inaccurate description about packet generator(scapy or ixia)
> - fix inaccurate description about mixed streams
> - add more description about multiple streams.
> - remove No nic type limitation description.
> - add supported nics description.
>
> v4:
> - fix inaccurate description
>
> v3:
> - Follow Lin Xueqin suggestion
> - remove burst packet type limitation
> - add functional test case support
> - remove ixia command description
>
> yufengmx (2):
> [examples/flow_classify]: upload test plan
> [examples/flow_classify]: add flow_classify_test_plan label
>
> test_plans/flow_classify_test_plan.rst | 332
> +++++++++++++++++++++++++++++++++
> test_plans/index.rst | 1 +
> 2 files changed, 333 insertions(+)
> create mode 100644 test_plans/flow_classify_test_plan.rst
>
> --
> 1.9.3
prev parent reply other threads:[~2019-06-26 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 8:19 yufengmx
2019-06-25 8:19 ` [dts] [PATCH V5 1/2] " yufengmx
2019-06-25 8:41 ` Lin, Xueqin
2019-06-25 8:19 ` [dts] [PATCH V5 2/2] [examples/flow_classify]: add flow_classify_test_plan label yufengmx
2019-06-26 8:10 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BAC51E1@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=yufengx.mo@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).