test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Ma, LihongX" <lihongx.ma@intel.com>
To: "Mo, YufengX" <yufengx.mo@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V2 0/2] flexible_rxd: add test cases for iavf/mpls
Date: Mon, 19 Oct 2020 05:16:41 +0000	[thread overview]
Message-ID: <BN8PR11MB3715731938F215E66D5C6E6C9E1E0@BN8PR11MB3715.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20201019050537.30009-1-yufengx.mo@intel.com>

Acked-by: Lihong Ma<lihongx.ma@intel.com>

Regards,
Ma,lihong

> -----Original Message-----
> From: Mo, YufengX <yufengx.mo@intel.com>
> Sent: Monday, October 19, 2020 1:06 PM
> To: dts@dpdk.org; Ma, LihongX <lihongx.ma@intel.com>
> Cc: Mo, YufengX <yufengx.mo@intel.com>
> Subject: [dts][PATCH V2 0/2] flexible_rxd: add test cases for iavf/mpls
> 
> 
> v2:
>  -  update iavf test content
>  -  change the 'flex_desc' to 'proto_xtr' when start testpmd.
>  -  change check_IPv4_IPv6_TCP_fields_in_RXD_on_specific_queues RXDIDs.
> 
> v1:
>  - add test cases for iavf/mpls.
> 
> yufengmx (2):
>   flexible_rxd: unify common test content
>   flexible_rxd: add mpls test cases
> 
>  tests/TestSuite_flexible_rxd.py | 255 +++++++----------
>  tests/flexible_common.py        | 482 ++++++++++++++++++++++++++++++++
>  2 files changed, 578 insertions(+), 159 deletions(-)  create mode 100644
> tests/flexible_common.py
> 
> --
> 2.21.0


      parent reply	other threads:[~2020-10-19  5:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19  5:05 yufengmx
2020-10-19  5:05 ` [dts] [PATCH V2 1/2] flexible_rxd: unify common test content yufengmx
2020-10-19  5:05 ` [dts] [PATCH V2 2/2] flexible_rxd: add mpls test cases yufengmx
2020-10-19  5:12 ` [dts] [PATCH V2 0/2] flexible_rxd: add test cases for iavf/mpls Mo, YufengX
2020-10-19  5:16 ` Ma, LihongX [this message]

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=BN8PR11MB3715731938F215E66D5C6E6C9E1E0@BN8PR11MB3715.namprd11.prod.outlook.com \
    --to=lihongx.ma@intel.com \
    --cc=dts@dpdk.org \
    --cc=yufengx.mo@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).