From: Hailin Xu <hailinx.xu@intel.com>
To: dts@dpdk.org
Cc: xueqin.lin@intel.com, Hailin Xu <hailinx.xu@intel.com>
Subject: [dts] [PATCH v1 0/2] add new test plans and test cases
Date: Thu, 3 Jun 2021 22:28:59 +0800 [thread overview]
Message-ID: <20210603142901.11181-1-hailinx.xu@intel.com> (raw)
Add fdir with gtpu inner l3/l4 cases.
Hailin Xu (2):
test_plans/iavf_fdir: add gtpu inner l3/l4 test plans
tests/iavf_fdir: add gtpu inner l3/l4 test cases
test_plans/iavf_fdir_test_plan.rst | 1725 ++++++++-
tests/TestSuite_iavf_fdir.py | 5512 +++++++++++++++++++++++++++-
2 files changed, 7019 insertions(+), 218 deletions(-)
--
2.17.1
next reply other threads:[~2021-06-03 6:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 14:28 Hailin Xu [this message]
2021-06-03 14:29 ` [dts] [PATCH v1 1/2] test_plans/iavf_fdir: add new test plans Hailin Xu
2021-06-07 9:07 ` Lin, Xueqin
2021-06-03 14:29 ` [dts] [PATCH v1 2/2] tests/iavf_fdir: add new test cases Hailin Xu
2021-06-03 7:06 ` Xu, HailinX
2021-06-07 9:23 ` Lin, Xueqin
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=20210603142901.11181-1-hailinx.xu@intel.com \
--to=hailinx.xu@intel.com \
--cc=dts@dpdk.org \
--cc=xueqin.lin@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).