test suite reviews and discussions
 help / color / mirror / Atom feed
From: Song Jiale <songx.jiale@intel.com>
To: dts@dpdk.org
Cc: Song Jiale <songx.jiale@intel.com>
Subject: [dts] [PATCH V2 0/5] split the ice_qinq suite
Date: Wed, 11 Jan 2023 10:38:53 +0000	[thread overview]
Message-ID: <20230111103858.970228-1-songx.jiale@intel.com> (raw)

split the cases in ice_qinq to ice_dcf_dual_vlan and kernelpf_iavf.

Song Jiale (5):
  tests/ice_dcf_dual_vlan: split the test suite of ice_qinq
  tests/kernelpf_iavf: split the test suite of ice_qinq
  test_plans/ice_dcf_dual_vlan: split the test suite of ice_qinq
  test_plans/kernelpf_iavf: split the test suite of ice_qinq
  test_plans/index: split the test suite of ice_qinq

 ...an.rst => ice_dcf_dual_vlan_test_plan.rst} | 1695 +++++------------
 test_plans/index.rst                          |    2 +-
 test_plans/kernelpf_iavf_test_plan.rst        |  574 ++++++
 ...qinq.py => TestSuite_ice_dcf_dual_vlan.py} |  653 ++-----
 tests/TestSuite_kernelpf_iavf.py              |  361 +++-
 5 files changed, 1580 insertions(+), 1705 deletions(-)
 rename test_plans/{ice_qinq_test_plan.rst => ice_dcf_dual_vlan_test_plan.rst} (64%)
 rename tests/{TestSuite_ice_qinq.py => TestSuite_ice_dcf_dual_vlan.py} (67%)

-- 
2.25.1


             reply	other threads:[~2023-01-11  2:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-11 10:38 Song Jiale [this message]
2023-01-11 10:38 ` [dts] [PATCH V2 1/5] tests/ice_dcf_dual_vlan: " Song Jiale
2023-01-11 10:38 ` [dts] [PATCH V2 2/5] tests/kernelpf_iavf: split the test suite of ice_qinq Song Jiale
2023-01-11 10:38 ` [dts] [PATCH V2 3/5] test_plans/ice_dcf_dual_vlan: split ice_qinq suite Song Jiale
2023-01-11 10:38 ` [dts] [PATCH V2 4/5] test_plans/kernelpf_iavf: split the test suite of ice_qinq Song Jiale
2023-01-11 10:38 ` [dts] [PATCH V2 5/5] test_plans/index: " Song Jiale
2023-01-11  5:45   ` lijuan.tu

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=20230111103858.970228-1-songx.jiale@intel.com \
    --to=songx.jiale@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).