From: "Peng, Yuan" <yuan.peng@intel.com>
To: "Di, ChenxuX" <chenxux.di@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Peng, Yuan" <yuan.peng@intel.com>
Subject: Re: [dts] [PATCH v6 0/2] add fortville rss input test
Date: Fri, 17 Apr 2020 07:21:24 +0000 [thread overview]
Message-ID: <BY5PR11MB3893F1ABA236BBC2F7BCC518FED90@BY5PR11MB3893.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200417033334.62166-1-chenxux.di@intel.com>
Acked by Peng, Yuan <yuan.peng@intel.com>
-----Original Message-----
From: Di, ChenxuX <chenxux.di@intel.com>
Sent: Friday, April 17, 2020 11:34 AM
To: dts@dpdk.org
Cc: Peng, Yuan <yuan.peng@intel.com>; Di, ChenxuX <chenxux.di@intel.com>
Subject: [PATCH v6 0/2] add fortville rss input test
add fortville rss input test plan
add fortville rss input test suite
--
v6:
-Fixed mistake about validate rule
v5:
-Fixed bug about ipv4-udp and ipv4-sctp packet
v4:
-Updated the test plan and test suite about hash function
v3:
-Update the test plan about all input set
v2:
-Updated the test plan and test suite about all inputset -Added test suite about hash global configuration
Chenxu Di (2):
test_plans/fortville_rss_input: add fortville rss input test plan
tests/fortville_rss_input: add fortville rss input
test_plans/fortville_rss_input_test_plan.rst | 600 +++
tests/TestSuite_fortville_rss_input.py | 3987 ++++++++++++++++++
2 files changed, 4587 insertions(+)
create mode 100644 test_plans/fortville_rss_input_test_plan.rst
create mode 100644 tests/TestSuite_fortville_rss_input.py
--
2.17.1
next prev parent reply other threads:[~2020-04-17 7:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 3:33 Chenxu Di
2020-04-17 3:33 ` [dts] [PATCH v6 1/2] test_plans/fortville_rss_input: add fortville rss input test plan Chenxu Di
2020-04-17 3:33 ` [dts] [PATCH v6 2/2] tests/fortville_rss_input: add fortville rss input Chenxu Di
2020-04-17 7:21 ` Peng, Yuan [this message]
2020-04-20 5:23 ` [dts] [PATCH v6 0/2] add fortville rss input test Tu, Lijuan
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=BY5PR11MB3893F1ABA236BBC2F7BCC518FED90@BY5PR11MB3893.namprd11.prod.outlook.com \
--to=yuan.peng@intel.com \
--cc=chenxux.di@intel.com \
--cc=dts@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).