From: "Ma, LihongX" <lihongx.ma@intel.com>
To: "Zeng, XiaoxiaoX" <xiaoxiaox.zeng@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: "Zeng, XiaoxiaoX" <xiaoxiaox.zeng@intel.com>
Subject: Re: [dts] [PATCH V1] conf/test_case_checklist: add columbiaville_100g not support info
Date: Wed, 27 Nov 2019 02:35:18 +0000 [thread overview]
Message-ID: <BE1E572D0441E34284F1F8B7AC28F1970BB29490@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20191125212712.28746-1-xiaoxiaox.zeng@intel.com>
Hi,xiaoxiao
About cases in dual_vlan, not only reference about columbiaville_100g, also reference to columbiaville_25G, I think it is better modify together.
About vlan_ethertype_config, all the cases in the suite not support CVL, I think you can add the check in suite.
-----Original Message-----
From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Xiaoxiao Zeng
Sent: Tuesday, November 26, 2019 5:27 AM
To: dts@dpdk.org
Cc: Zeng, XiaoxiaoX <xiaoxiaox.zeng@intel.com>
Subject: [dts] [PATCH V1] conf/test_case_checklist: add columbiaville_100g not support info
Signed-off-by: Xiaoxiao Zeng <xiaoxiaox.zeng@intel.com>
---
conf/test_case_checklist.json | 126 ++++++++++++++++++++++++++++++++--
1 file changed, 119 insertions(+), 7 deletions(-)
diff --git a/conf/test_case_checklist.json b/conf/test_case_checklist.json index ffafaf4..48819ee 100644
--- a/conf/test_case_checklist.json
+++ b/conf/test_case_checklist.json
@@ -277,7 +277,8 @@
"fortpark_TLV",
"cavium_a063",
"cavium_a064",
- "carlsville"
+ "carlsville",
+ "columbiaville_100g"
],
"Target": [
"ALL"
@@ -300,7 +301,8 @@
"cavium_a063",
"cavium_a064",
"carlsville",
- "powerville"
+ "powerville",
+ "columbiaville_100g"
],
"Target": [
"ALL"
@@ -511,7 +513,8 @@
"fortpark_TLV",
"sagepond",
"sageville",
- "carlsville"
+ "carlsville",
+ "columbiaville_100g"
],
"Target": [
"ALL"
@@ -533,7 +536,8 @@
"fortpark_TLV",
"sagepond",
"sageville",
- "carlsville"
+ "carlsville",
+ "columbiaville_100g"
],
"Target": [
"ALL"
@@ -2150,7 +2154,8 @@
"fortville_25g",
"fortpark_TLV",
"cavium_a064",
- "carlsville"
+ "carlsville",
+ "columbiaville_100g"
],
"Target": [
"ALL"
@@ -2342,7 +2347,8 @@
],
"NIC": [
"cavium_a063",
- "cavium_a064"
+ "cavium_a064",
+ "columbiaville_100g"
],
"Target": [
"ALL"
@@ -2413,5 +2419,111 @@
"Bug ID": "",
"Comments": "the nic not support this case: ice_dev_filter_ctrl(): Filter type (6) not supported"
}
- ]
+ ],
+ "l2pkt_detect": [
+ {
+ "OS": [
+ "ALL"
+ ],
+ "NIC": [
+ "columbiaville_100g"
+ ],
+ "Target": [
+ "ALL"
+ ],
+ "Bug ID": "",
+ "Comments": "the nic not support this case"
+ }
+ ],
+ "GRE_ipv6_packet_detect": [
+ {
+ "OS": [
+ "ALL"
+ ],
+ "NIC": [
+ "columbiaville_100g"
+ ],
+ "Target": [
+ "ALL"
+ ],
+ "Bug ID": "",
+ "Comments": "the nic not support this case"
+ }
+ ],
+ "vlan_add_vlan_tag": [
+ {
+ "OS": [
+ "ALL"
+ ],
+ "NIC": [
+ "columbiaville_100g"
+ ],
+ "Target": [
+ "ALL"
+ ],
+ "Bug ID": "",
+ "Comments": "the nic not support this case"
+ }
+ ],
+ "vlan_strip": [
+ {
+ "OS": [
+ "ALL"
+ ],
+ "NIC": [
+ "columbiaville_100g"
+ ],
+ "Target": [
+ "ALL"
+ ],
+ "Bug ID": "",
+ "Comments": "the nic not support this case"
+ }
+ ],
+ "vlan_filter_on_off": [
+ {
+ "OS": [
+ "ALL"
+ ],
+ "NIC": [
+ "columbiaville_100g"
+ ],
+ "Target": [
+ "ALL"
+ ],
+ "Bug ID": "",
+ "Comments": "the nic not support this case"
+ }
+ ],
+ "vlan_enable_vlan_insertion": [
+ {
+ "OS": [
+ "ALL"
+ ],
+ "NIC": [
+ "columbiaville_100g"
+ ],
+ "Target": [
+ "ALL"
+ ],
+ "Bug ID": "",
+ "Comments": "the nic not support this case"
+ }
+ ],
+ "link_status_interrupt_change": [
+ {
+ "OS": [
+ "ALL"
+ ],
+ "NIC": [
+ "columbiaville_100g"
+ ],
+ "Target": [
+ "ALL"
+ ],
+ "Bug ID": "",
+ "Comments": "the nic not support this case"
+ }
+ ]
+
}
--
2.17.0
prev parent reply other threads:[~2019-11-27 2:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 21:27 Xiaoxiao Zeng
2019-11-27 2:35 ` Ma, LihongX [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=BE1E572D0441E34284F1F8B7AC28F1970BB29490@SHSMSX101.ccr.corp.intel.com \
--to=lihongx.ma@intel.com \
--cc=dts@dpdk.org \
--cc=xiaoxiaox.zeng@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).