test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Zhao, XinfengX" <xinfengx.zhao@intel.com>
To: "dts@dpdk.org" <dts@dpdk.org>
Cc: "Xu, HailinX" <hailinx.xu@intel.com>
Subject: Re: [dts] [PATCH v1]conf/test_case_checklist.json:carlsville not	support cases.
Date: Fri, 17 Apr 2020 05:14:10 +0000	[thread overview]
Message-ID: <e2dee536141b4d2cb35cc0ed5c9c75d9@intel.com> (raw)
In-Reply-To: <1586746332-120212-1-git-send-email-hailinx.xu@intel.com>

Tested-by:  Zhao, Xinfeng<xinfengx.zhao@intel.com>

-----Original Message-----
From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Xu Hailin
Sent: Monday, April 13, 2020 10:52 AM
To: dts@dpdk.org
Cc: Xu, HailinX <hailinx.xu@intel.com>
Subject: [dts] [PATCH v1]conf/test_case_checklist.json:carlsville not support cases.

From: xuhailin <hailinx.xu@intel.com>

carlsville nic driver is i40e,so not support userspace_ethtool/port_mtu and userspace_ethtool/retrieve_reg.

Signed-off-by: xuhailin <hailinx.xu@intel.com>
---
 conf/test_case_checklist.json | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/conf/test_case_checklist.json b/conf/test_case_checklist.json index 1a2d93ca..4dea9d90 100644
--- a/conf/test_case_checklist.json
+++ b/conf/test_case_checklist.json
@@ -1999,7 +1999,8 @@
                 "fortville_25g",
                 "fortpark",
                 "fortpark_TLV",
-                "fortpark_TLV_vf"
+                "fortpark_TLV_vf",
+		"carlsville"
             ],
             "Target": [
                 "ALL"
@@ -2259,7 +2260,8 @@
                 "fortpark_TLV_vf",
                 "cavium_a064",
                 "columbiaville_25g",
-                "columbiaville_100g"
+                "columbiaville_100g",
+		"carlsville"
             ],
             "Target": [
                 "ALL"
--
2.17.1


  reply	other threads:[~2020-04-17  5:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-13  2:52 Xu Hailin
2020-04-17  5:14 ` Zhao, XinfengX [this message]
2020-04-20  4:54 ` 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=e2dee536141b4d2cb35cc0ed5c9c75d9@intel.com \
    --to=xinfengx.zhao@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).