test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "He, Zhiwei" <zhiwei.he@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: root <root@dpdktestzhiwei171.sh.intel.com>
Subject: Re: [dts] [PATCH V3] conf/test_case_supportlist: Add CVL25G&100G enable	in support list for the l2pkt and gre case
Date: Wed, 4 Sep 2019 03:02:55 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BB1AC94@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1567153733-18158-1-git-send-email-zhiwei.he@intel.com>

Applied, thanks

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of zhiwei.he
> Sent: Friday, August 30, 2019 4:29 PM
> To: dts@dpdk.org
> Cc: root <root@dpdktestzhiwei171.sh.intel.com>
> Subject: [dts] [PATCH V3] conf/test_case_supportlist: Add CVL25G&100G
> enable in support list for the l2pkt and gre case
> 
> From: root <root@dpdktestzhiwei171.sh.intel.com>
> 
> Signed-off-by: root <root@dpdktestzhiwei171.sh.intel.com>
> ---
>  conf/test_case_supportlist.json | 20 +++++++++++++++-----
>  1 file changed, 15 insertions(+), 5 deletions(-)
> 
> diff --git a/conf/test_case_supportlist.json b/conf/test_case_supportlist.json
> index d5cbb01..1f443f6 100644
> --- a/conf/test_case_supportlist.json
> +++ b/conf/test_case_supportlist.json
> @@ -134,7 +134,9 @@
>                  "fortville_spirit",
>                  "fortville_spirit_single",
>                  "fortville_25g",
> -	        "carlsville"
> +	        "carlsville",
> +                "columbiaville_25g",
> +                "columbiaville_100g"
>              ],
>              "Target": [
>                  "ALL"
> @@ -154,7 +156,9 @@
>                  "fortville_spirit",
>                  "fortville_spirit_single",
>                  "fortville_25g",
> -		"carlsville"
> +		"carlsville",
> +                "columbiaville_25g",
> +                "columbiaville_100g"
>              ],
>              "Target": [
>                  "ALL"
> @@ -176,7 +180,9 @@
>                  "fortville_spirit",
>                  "fortville_spirit_single",
>  		"fortpark_TLV",
> -	        "carlsville"
> +	        "carlsville",
> +                "columbiaville_25g",
> +                "columbiaville_100g"
>              ],
>              "Target": [
>                  "ALL"
> @@ -196,7 +202,9 @@
>                  "fortville_spirit",
>                  "fortville_spirit_single",
>                  "fortville_25g",
> -                "carlsville"
> +                "carlsville",
> +                "columbiaville_25g",
> +                "columbiaville_100g"
>              ],
>              "Target": [
>                  "ALL"
> @@ -256,7 +264,9 @@
>                  "fortville_spirit",
>                  "fortville_spirit_single",
>                  "fortville_25g",
> -		"carlsville"
> +		"carlsville",
> +                "columbiaville_25g",
> +                "columbiaville_100g"
>              ],
>              "Target": [
>                  "ALL"
> --
> 1.8.3.1


      reply	other threads:[~2019-09-04  3:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-30  8:28 zhiwei.he
2019-09-04  3:02 ` Tu, Lijuan [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=8CE3E05A3F976642AAB0F4675D0AD20E0BB1AC94@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=root@dpdktestzhiwei171.sh.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).