test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Fu, Qi" <qi.fu@intel.com>
To: "Jiale, SongX" <songx.jiale@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Jiale, SongX" <songx.jiale@intel.com>
Subject: RE: [dts] [PATCH V1 4/4] tests/ice_iavf_dual_vlan: split test suite
Date: Tue, 13 Sep 2022 08:33:00 +0000	[thread overview]
Message-ID: <DM6PR11MB4611E6C9488E811AE4E77C54EA479@DM6PR11MB4611.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220907170656.2551-4-songx.jiale@intel.com>

> -----Original Message-----
> From: Song Jiale <songx.jiale@intel.com>
> Sent: Thursday, September 8, 2022 1:07 AM
> To: dts@dpdk.org
> Cc: Jiale, SongX <songx.jiale@intel.com>
> Subject: [dts] [PATCH V1 4/4] tests/ice_iavf_dual_vlan: split test suite
> 
> split the test suite of ice_qinq into ice_dcf_dual_vlan and ice_iavf_dual_vlan.
> 
> Signed-off-by: Song Jiale <songx.jiale@intel.com>
> ---
>  tests/TestSuite_ice_iavf_dual_vlan.py | 496 ++++++++++++++++++++++++++
>  1 file changed, 496 insertions(+)
>  create mode 100644 tests/TestSuite_ice_iavf_dual_vlan.py

Acked-by: Fu, Qi <qi.fu@intel.com>


  reply	other threads:[~2022-09-13  8:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07 17:06 [dts] [PATCH V1 1/4] test_plans/ice_dcf_dual_vlan: " Song Jiale
2022-09-07 17:06 ` [dts] [PATCH V1 2/4] test_plans/ice_iavf_dual_vlan: " Song Jiale
2022-09-13  8:56   ` Fu, Qi
2022-09-07 17:06 ` [dts] [PATCH V1 3/4] tests/ice_dcf_dual_vlan: " Song Jiale
2022-09-13  8:58   ` Fu, Qi
2022-09-07 17:06 ` [dts] [PATCH V1 4/4] tests/ice_iavf_dual_vlan: " Song Jiale
2022-09-13  8:33   ` Fu, Qi [this message]
2022-09-13  8:35 ` [dts] [PATCH V1 1/4] test_plans/ice_dcf_dual_vlan: " Fu, Qi
  -- strict thread matches above, loose matches on Subject: below --
2022-09-07 13:54 Song Jiale
2022-09-07 13:54 ` [dts] [PATCH V1 4/4] tests/ice_iavf_dual_vlan: " Song Jiale

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=DM6PR11MB4611E6C9488E811AE4E77C54EA479@DM6PR11MB4611.namprd11.prod.outlook.com \
    --to=qi.fu@intel.com \
    --cc=dts@dpdk.org \
    --cc=songx.jiale@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).