test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Zhang, XiX" <xix.zhang@intel.com>
To: "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V1] conf/test_case_checklist:i40e not support change speed on kernel driver
Date: Thu, 4 Jun 2020 02:15:52 +0000	[thread overview]
Message-ID: <E22AF82976AEF646B9B29E4604B9BED504CB23DC@CDSMSX102.ccr.corp.intel.com> (raw)
In-Reply-To: <1591237214-10170-1-git-send-email-xix.zhang@intel.com>

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

Tested-by: zhang,xi <xix.zhang@intel.com>

-----Original Message-----
From: Zhang, XiX 
Sent: Thursday, June 4, 2020 10:20 AM
To: dts@dpdk.org
Cc: Zhang, XiX <xix.zhang@intel.com>
Subject: [dts][PATCH V1] conf/test_case_checklist:i40e not support change speed on kernel driver

i40e not support change speed on kernel driver 

Signed-off-by: xizhan4x <xix.zhang@intel.com>
---
 conf/test_case_checklist.json | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/conf/test_case_checklist.json b/conf/test_case_checklist.json index 73eda68..48c7c5e 100644
--- a/conf/test_case_checklist.json
+++ b/conf/test_case_checklist.json
@@ -3425,5 +3425,27 @@
             "Bug ID": "",
             "Comments": "32 bites not support this case(memoory not enough)."
         }
+    ],
+    "change_linkspeed_vf": [
+        {
+            "OS": [
+                "ALL"
+            ],
+            "NIC": [
+                "fortville_eagle",
+                "fortville_spirit",
+	        "fortville_spirit_single",
+	        "fortpark",
+	        "fortpark_TLV",
+	        "fortville_25g",
+	        "carlsville"
+	        	
+            ],
+            "Target": [
+                "ALL"
+            ],
+            "Bug ID": "",
+            "Comments": "ethtool not support change speed on i40e"
+        }
     ]
 }
--
2.17.2


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

04/06/2020 18:35:18                            dts: 
TEST SUITE : TestShutdownApi
04/06/2020 18:35:18                            dts: NIC :        fortville_25g
04/06/2020 18:35:18             dut.10.240.183.197: 
04/06/2020 18:35:18                         tester: 
04/06/2020 18:35:18                         tester: ifconfig ens10 mtu 5000
04/06/2020 18:35:18                         tester: 
04/06/2020 18:35:18                TestShutdownApi: Test Case test_change_linkspeed_vf Result SKIPPED:
04/06/2020 18:35:18                            dts: 
TEST SUITE ENDED: TestShutdownApi

      reply	other threads:[~2020-06-04  2:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-04  2:20 xizhan4x
2020-06-04  2:15 ` Zhang, XiX [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=E22AF82976AEF646B9B29E4604B9BED504CB23DC@CDSMSX102.ccr.corp.intel.com \
    --to=xix.zhang@intel.com \
    --cc=dts@dpdk.org \
    /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).