test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Xu, HailinX" <hailinx.xu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Xu, HailinX" <hailinx.xu@intel.com>
Subject: Re: [dts] [PATCH v1] conf/test_case_checklist:add nic carlsville
Date: Thu, 23 Apr 2020 05:42:49 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BC0F0DE@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1587467343-275327-1-git-send-email-hailinx.xu@intel.com>

Applied, thanks

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Xu Hailin
> Sent: Tuesday, April 21, 2020 7:09 PM
> To: dts@dpdk.org
> Cc: Xu, HailinX <hailinx.xu@intel.com>
> Subject: [dts] [PATCH v1] conf/test_case_checklist:add nic carlsville
> 
> From: "Xu, Hailin" <hailinx.xu@intel.com>
> 
> carlsville not support this case.
> 
> Signed-off-by: Xu, Hailin <hailinx.xu@intel.com>
> ---
>  conf/test_case_checklist.json | 10 +++++++---
>  1 file changed, 7 insertions(+), 3 deletions(-)
> 
> diff --git a/conf/test_case_checklist.json b/conf/test_case_checklist.json
> index d29d235..b2e93aa 100644
> --- a/conf/test_case_checklist.json
> +++ b/conf/test_case_checklist.json
> @@ -2063,7 +2063,8 @@
>                  "fortpark",
>                  "fortpark_TLV",
>                  "fortpark_BASE-T",
> -                "fortpark_TLV_vf"
> +                "fortpark_TLV_vf",
> +                "carlsville"
>              ],
>              "Target": [
>                  "ALL"
> @@ -2156,7 +2157,8 @@
>                  "fortville_eagle",
>                  "fortville_spirit",
>                  "fortville_spirit_single",
> -                "fortville_25g"
> +                "fortville_25g",
> +                "carlsville"
>              ],
>              "Target": [
>                  "ALL"
> @@ -2204,7 +2206,8 @@
>                  "fortville_eagle",
>                  "fortville_spirit",
>                  "fortville_spirit_single",
> -                "fortville_25g"
> +                "fortville_25g",
> +                "carlsville"
>              ],
>              "Target": [
>                  "ALL"
> @@ -2326,6 +2329,7 @@
>                  "cavium_a064",
>                  "columbiaville_25g",
>                  "columbiaville_100g",
> +                "carlsville",
>  		"foxville"
>              ],
>              "Target": [
> --
> 1.8.3.1


      parent reply	other threads:[~2020-04-23  5:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 11:09 Xu Hailin
2020-04-22  2:25 ` Zhao, XinfengX
2020-04-23  5:42 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BC0F0DE@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@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).