test suite reviews and discussions
 help / color / mirror / Atom feed
From: Lingli Chen <linglix.chen@intel.com>
To: dts@dpdk.org
Cc: zhiminx.huang@intel.com, Lingli Chen <linglix.chen@intel.com>
Subject: [dts][PATCH V1 0/3] add NIC IGC-I226_LM in support cases
Date: Fri, 24 Jun 2022 01:39:00 -0400	[thread overview]
Message-ID: <20220624053903.4195-1-linglix.chen@intel.com> (raw)

Lingli Chen (3):
  framework: add NIC IGC-I226_LM identifiers
  conf/test_case_*: add NIC IGC-I226_LM in support cases
  tests/*: add NIC IGC-I226_LM in support suits

 conf/test_case_checklist.json            | 53 ++++++++++++++----------
 conf/test_case_supportlist.json          | 23 +++++++---
 framework/settings.py                    |  2 +
 test_plans/shutdown_api_test_plan.rst    |  2 +-
 tests/TestSuite_generic_flow_api.py      | 26 +++++++++---
 tests/TestSuite_jumboframes.py           |  1 +
 tests/TestSuite_mtu_update.py            |  2 +-
 tests/TestSuite_pmdrss_hash.py           |  1 +
 tests/TestSuite_pmdrssreta.py            |  7 ++--
 tests/TestSuite_qinq_filter.py           |  1 +
 tests/TestSuite_rss_to_rte_flow.py       | 31 +++++++-------
 tests/TestSuite_rxtx_offload.py          |  4 +-
 tests/TestSuite_shutdown_api.py          |  8 ++--
 tests/TestSuite_uni_pkt.py               |  3 ++
 tests/TestSuite_userspace_ethtool.py     |  3 +-
 tests/TestSuite_vlan_ethertype_config.py |  8 ++--
 16 files changed, 111 insertions(+), 64 deletions(-)

-- 
2.17.1


             reply	other threads:[~2022-06-24  6:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24  5:39 Lingli Chen [this message]
2022-06-24  5:39 ` [dts][PATCH V1 1/3] framework: add NIC IGC-I226_LM identifiers Lingli Chen
2022-06-24  5:39 ` [dts][PATCH V1 2/3] conf/test_case_*: add NIC IGC-I226_LM in support cases Lingli Chen
2022-06-24  5:39 ` [dts][PATCH V1 3/3] tests/*: add NIC IGC-I226_LM in support suits Lingli Chen

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=20220624053903.4195-1-linglix.chen@intel.com \
    --to=linglix.chen@intel.com \
    --cc=dts@dpdk.org \
    --cc=zhiminx.huang@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).