test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Fu, Qi" <qi.fu@intel.com>
To: "Xu, HailinX" <hailinx.xu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: RE: [dts][PATCH v2 2/2] tests/ice_fdir: support ipv6 next proto id
Date: Wed, 14 Sep 2022 07:55:10 +0000	[thread overview]
Message-ID: <DM6PR11MB46111129CF0DD604038D60ECEA469@DM6PR11MB4611.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220914073951.29759-3-hailinx.xu@intel.com>

> -----Original Message-----
> From: Xu, HailinX <hailinx.xu@intel.com>
> Sent: Wednesday, September 14, 2022 3:40 PM
> To: dts@dpdk.org; Fu, Qi <qi.fu@intel.com>
> Cc: Xu, HailinX <hailinx.xu@intel.com>
> Subject: [dts][PATCH v2 2/2] tests/ice_fdir: support ipv6 next proto id
> 
> add new test cases for ice support ipv6 next proto id
> 
> Signed-off-by: hailinx xu <hailinx.xu@intel.com>
> ---
>  tests/TestSuite_ice_fdir.py | 336 ++++++++++++++++++++++++++++++++++++
>  1 file changed, 336 insertions(+)
> 
Acked-by: Fu, Qi <qi.fu@intel.com>

  parent reply	other threads:[~2022-09-14  7:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14  7:39 [dts][PATCH v2 0/2] add new test plans and test cases hailinx xu
2022-09-14  7:39 ` [dts][PATCH v2 1/2] test_plans/ice_fdir: support ipv6 next proto id hailinx xu
2022-09-14  7:54   ` Fu, Qi
2022-09-20  8:37   ` Fu, Qi
2022-09-14  7:39 ` [dts][PATCH v2 2/2] tests/ice_fdir: " hailinx xu
2022-09-14  7:52   ` Huang, ZhiminX
2022-09-14  7:55   ` Fu, Qi [this message]
2022-09-20  8:37   ` Fu, Qi
  -- strict thread matches above, loose matches on Subject: below --
2022-09-09 10:16 [dts][PATCH v2 0/2] add new test plans and test cases hailinx xu
2022-09-09 10:16 ` [dts][PATCH v2 2/2] tests/ice_fdir: support ipv6 next proto id hailinx xu

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