test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Li, WenjieX A" <wenjiex.a.li@intel.com>
To: "Zeng, XiaoxiaoX" <xiaoxiaox.zeng@intel.com>,
	"dts@dpdk.org" <dts@dpdk.org>
Cc: "Zeng, XiaoxiaoX" <xiaoxiaox.zeng@intel.com>,
	"Li, WenjieX A" <wenjiex.a.li@intel.com>
Subject: Re: [dts] [PATCH V3] conf/test_case_checklist: add dual_vlan checklist	for cvl
Date: Thu, 5 Dec 2019 06:16:03 +0000	[thread overview]
Message-ID: <8688172CD5C0B74590FAE19D9579F94B53802830@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <20191205180815.8707-1-xiaoxiaox.zeng@intel.com>

[-- Attachment #1: Type: text/plain, Size: 2234 bytes --]

Tested-by: Li, WenjieX A <wenjiex.a.li@intel.com>

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Xiaoxiao Zeng
> Sent: Friday, December 6, 2019 2:08 AM
> To: dts@dpdk.org
> Cc: Zeng, XiaoxiaoX <xiaoxiaox.zeng@intel.com>
> Subject: [dts] [PATCH V3] conf/test_case_checklist: add dual_vlan checklist for
> cvl
> 
> *for cases :
> vlan_synthetic_test/vlan_tpid_config/vlan_stripq_config/vlan_random_test.
> 
> Signed-off-by: Xiaoxiao Zeng <xiaoxiaox.zeng@intel.com>
> ---
>  conf/test_case_checklist.json | 16 ++++++++++++----
>  1 file changed, 12 insertions(+), 4 deletions(-)
> 
> diff --git a/conf/test_case_checklist.json b/conf/test_case_checklist.json index
> 38b1335..4ad4b65 100644
> --- a/conf/test_case_checklist.json
> +++ b/conf/test_case_checklist.json
> @@ -277,7 +277,9 @@
>                  "fortpark_TLV",
>                  "cavium_a063",
>                  "cavium_a064",
> -                "carlsville"
> +                "carlsville",
> +                "columbiaville_25g",
> +                "columbiaville_100g"
>              ],
>              "Target": [
>                  "ALL"
> @@ -300,7 +302,9 @@
>                  "cavium_a063",
>                  "cavium_a064",
>                  "carlsville",
> -                "powerville"
> +                "powerville",
> +                "columbiaville_25g",
> +                "columbiaville_100g"
>              ],
>              "Target": [
>                  "ALL"
> @@ -513,7 +517,9 @@
>                  "fortpark_TLV",
>                  "sagepond",
>                  "sageville",
> -                "carlsville"
> +                "carlsville",
> +                "columbiaville_25g",
> +                "columbiaville_100g"
>              ],
>              "Target": [
>                  "ALL"
> @@ -535,7 +541,9 @@
>                  "fortpark_TLV",
>                  "sagepond",
>                  "sageville",
> -                "carlsville"
> +                "carlsville",
> +                "columbiaville_25g",
> +                "columbiaville_100g"
>              ],
>              "Target": [
>                  "ALL"
> --
> 2.17.0


[-- Attachment #2: TestDualVlan.log --]
[-- Type: application/octet-stream, Size: 67914 bytes --]

  reply	other threads:[~2019-12-05  6:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05 18:08 Xiaoxiao Zeng
2019-12-05  6:16 ` Li, WenjieX A [this message]
2019-12-19  7:44 ` Tu, Lijuan

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=8688172CD5C0B74590FAE19D9579F94B53802830@SHSMSX103.ccr.corp.intel.com \
    --to=wenjiex.a.li@intel.com \
    --cc=dts@dpdk.org \
    --cc=xiaoxiaox.zeng@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).