From: hailinx xu <hailinx.xu@intel.com>
To: dts@dpdk.org, qi.fu@intel.com
Cc: hailinx xu <hailinx.xu@intel.com>
Subject: [dts][PATCH v3 0/2] add new test plans and test cases
Date: Thu, 22 Sep 2022 13:28:37 +0800 [thread overview]
Message-ID: <20220922052839.23851-1-hailinx.xu@intel.com> (raw)
v1: add new test plans/cases for ice support ipv6 next protocol id
v2:
1. Modify case name.
2. update Pattern table.
3. Refine test plans steps.
v3: Fix patch apply issue.
hailinx xu (2):
test_plans: support ipv6 next proto id
tests/ice_fdir: support ipv6 next proto id
test_plans/ice_fdir_test_plan.rst | 418 ++++++++++++++++++++++++++----
tests/TestSuite_ice_fdir.py | 336 ++++++++++++++++++++++++
2 files changed, 701 insertions(+), 53 deletions(-)
--
2.17.1
next reply other threads:[~2022-09-22 5:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 5:28 hailinx xu [this message]
2022-09-22 5:28 ` [dts][PATCH v3 1/2] test_plans: support ipv6 next proto id hailinx xu
2022-09-28 5:46 ` lijuan.tu
2022-09-22 5:28 ` [dts][PATCH v3 2/2] tests/ice_fdir: " hailinx xu
2022-09-22 8:50 ` Huang, ZhiminX
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=20220922052839.23851-1-hailinx.xu@intel.com \
--to=hailinx.xu@intel.com \
--cc=dts@dpdk.org \
--cc=qi.fu@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).