test suite reviews and discussions
 help / color / mirror / Atom feed
From: Chen Lingli <linglix.chen@intel.com>
To: dts@dpdk.org
Cc: Chen Lingli <linglix.chen@intel.com>
Subject: [dts] [PATCH V1] conf/test_case_checklist:add NIC not support case
Date: Mon,  8 Mar 2021 17:47:40 +0000	[thread overview]
Message-ID: <20210308174740.387697-1-linglix.chen@intel.com> (raw)

1.generic_flow_api: add fortville_eagle not support case.
Comments:testpmd not support socket-mem and file-prefix param in
freebsd.
2.mtu_checks_100: add springville/powerville/foxville not support.

Signed-off-by: Chen Lingli <linglix.chen@intel.com>
---
 conf/test_case_checklist.json | 111 +++++++++++++++++++++++++++++++++-
 1 file changed, 110 insertions(+), 1 deletion(-)

diff --git a/conf/test_case_checklist.json b/conf/test_case_checklist.json
index 133700fc..04411b88 100644
--- a/conf/test_case_checklist.json
+++ b/conf/test_case_checklist.json
@@ -2953,6 +2953,19 @@
             ],
             "Bug ID": "",
             "Comments": "NIC not support this case"
+        },
+        {
+            "OS": [
+                "freebsd"
+            ],
+            "NIC": [
+                "fortville_eagle"
+            ],
+            "Target": [
+                "ALL"
+            ],
+            "Bug ID": "",
+            "Comments": "testpmd not support socket-mem and file-prefix param in freebsd"
         }
     ],
 	"fdir_for_nvgre": [
@@ -2968,6 +2981,19 @@
             ],
             "Bug ID": "",
             "Comments": "NIC not support this case"
+        },
+	{
+            "OS": [
+                "freebsd"
+            ],
+            "NIC": [
+                "fortville_eagle"
+            ],
+            "Target": [
+                "ALL"
+            ],
+            "Bug ID": "",
+            "Comments": "testpmd not support socket-mem and file-prefix param in freebsd"
         }
     ],
 	"L2_tunnel_filter": [
@@ -3195,6 +3221,19 @@
             ],
             "Bug ID": "",
             "Comments": "NIC not support this case"
+        },
+        {
+            "OS": [
+                "freebsd"
+            ],
+            "NIC": [
+                "fortville_eagle"
+            ],
+            "Target": [
+                "ALL"
+            ],
+            "Bug ID": "",
+            "Comments": "testpmd not support socket-mem and file-prefix param in freebsd"
         }
     ],
 	"fdir_for_flexbytes": [
@@ -3210,6 +3249,19 @@
             ],
             "Bug ID": "",
             "Comments": "NIC not support this case"
+        },
+        {
+            "OS": [
+                "freebsd"
+            ],
+            "NIC": [
+                "fortville_eagle"
+            ],
+            "Target": [
+                "ALL"
+            ],
+            "Bug ID": "",
+            "Comments": "testpmd not support socket-mem and file-prefix param in freebsd"
         }
     ],
 	"fdir_for_mac_vlan": [
@@ -3240,6 +3292,19 @@
             ],
             "Bug ID": "",
             "Comments": "NIC not support this case"
+        },
+        {
+            "OS": [
+                "freebsd"
+            ],
+            "NIC": [
+                "fortville_eagle"
+            ],
+            "Target": [
+                "ALL"
+            ],
+            "Bug ID": "",
+            "Comments": "testpmd not support socket-mem and file-prefix param in freebsd"
         }
     ],
 	"fdir_for_ipv4": [
@@ -3255,6 +3320,34 @@
             ],
             "Bug ID": "",
             "Comments": "NIC not support this case"
+        },
+        {
+            "OS": [
+                "freebsd"
+            ],
+            "NIC": [
+                "fortville_eagle"
+            ],
+            "Target": [
+                "ALL"
+            ],
+            "Bug ID": "",
+            "Comments": "testpmd not support socket-mem and file-prefix param in freebsd"
+        }
+    ],
+       "fdir_for_ipv6": [
+        {
+            "OS": [
+                "freebsd"
+            ],
+            "NIC": [
+                "fortville_eagle"
+            ],
+            "Target": [
+                "ALL"
+            ],
+            "Bug ID": "",
+            "Comments": "testpmd not support socket-mem and file-prefix param in freebsd"
         }
     ],
 	"fdir_for_vxlan": [
@@ -3270,6 +3363,19 @@
             ],
             "Bug ID": "",
             "Comments": "NIC not support this case"
+        },
+        {
+            "OS": [
+                "freebsd"
+            ],
+            "NIC": [
+                "fortville_eagle"
+            ],
+            "Target": [
+                "ALL"
+            ],
+            "Bug ID": "",
+            "Comments": "testpmd not support socket-mem and file-prefix param in freebsd"
         }
     ],
 	"link_status_interrupt_change": [
@@ -3579,7 +3685,10 @@
                  "niantic",
                  "twinpond",
                  "sageville",
-                 "sagepond"
+                 "sagepond",
+		 "springville",
+		 "powerville",
+                 "foxville"
              ],
              "Target": [
                  "ALL"
-- 
2.25.1


             reply	other threads:[~2021-03-08  9:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-08 17:47 Chen Lingli [this message]
2021-03-08  9:49 ` Chen, LingliX
2021-03-10  6:25 ` 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=20210308174740.387697-1-linglix.chen@intel.com \
    --to=linglix.chen@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).