test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Lin, Xueqin" <xueqin.lin@intel.com>
To: "He, Zhiwei" <zhiwei.he@intel.com>, "dts@dpdk.org" <dts@dpdk.org>,
	"Li, WenjieX A" <wenjiex.a.li@intel.com>
Cc: "He, Zhiwei" <zhiwei.he@intel.com>
Subject: Re: [dts] [PATCH V1] conf/test_case_supportlist : add limit for nvgre	ipv6 and ipv6 offload only suppor CVL
Date: Mon, 2 Sep 2019 09:11:01 +0000	[thread overview]
Message-ID: <0D300480287911409D9FF92C1FA2A3355B56635F@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1567412293-41996-1-git-send-email-zhiwei.he@intel.com>

Hi Wenjie&Zhiwei,

Not make sense to add the patch. Test plan has nvgre ipv6 relative cases, but script miss cases.
FVL should also support nvgre ipv6, pls check it.
If yes, pls also add nvgre ipv6 cases for FVL, thanks. 

Best regards,
Xueqin

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of zhiwei.he
> Sent: Monday, September 2, 2019 4:18 PM
> To: dts@dpdk.org
> Cc: He, Zhiwei <zhiwei.he@intel.com>
> Subject: [dts] [PATCH V1] conf/test_case_supportlist : add limit for nvgre
> ipv6 and ipv6 offload only suppor CVL
> 
> From: "zhiwei.he" <zhiwei.he@intel.com>
> 
> Signed-off-by: zhiwei.he <zhiwei.he@intel.com>
> ---
>  conf/test_case_supportlist.json | 32 ++++++++++++++++++++++++++++++++
>  1 file changed, 32 insertions(+)
> 
> diff --git a/conf/test_case_supportlist.json b/conf/test_case_supportlist.json
> index d5cbb01..974552b 100644
> --- a/conf/test_case_supportlist.json
> +++ b/conf/test_case_supportlist.json
> @@ -1598,5 +1598,37 @@
>              "Bug ID": "",
>              "Comments": "This case currently support for niantic "
>          }
> +    ],
> +    "nvgre_ipv6": [
> +        {
> +            "OS": [
> +                "ALL"
> +            ],
> +            "NIC": [
> +                "columbiaville_25g",
> +                "columbiaville_100g"
> +            ],
> +            "Target": [
> +                "ALL"
> +            ],
> +            "Bug ID": "",
> +            "Comments": "This case currently support for columbiaville "
> +        }
> +    ],
> +    "nvgre_ipv6_checksum_offload": [
> +        {
> +            "OS": [
> +                "ALL"
> +            ],
> +            "NIC": [
> +                "columbiaville_25g",
> +                "columbiaville_100g"
> +            ],
> +            "Target": [
> +                "ALL"
> +            ],
> +            "Bug ID": "",
> +            "Comments": "This case currently support for columbiaville "
> +        }
>      ]
>  }
> --
> 1.8.3.1


      reply	other threads:[~2019-09-02  9:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-02  8:18 zhiwei.he
2019-09-02  9:11 ` Lin, Xueqin [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=0D300480287911409D9FF92C1FA2A3355B56635F@SHSMSX104.ccr.corp.intel.com \
    --to=xueqin.lin@intel.com \
    --cc=dts@dpdk.org \
    --cc=wenjiex.a.li@intel.com \
    --cc=zhiwei.he@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).