From: "Zhu, WenhuiX" <wenhuix.zhu@intel.com>
To: "Yao, BingX Y" <bingx.y.yao@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Yao, BingX Y" <bingx.y.yao@intel.com>,
"Zhu, WenhuiX" <wenhuix.zhu@intel.com>
Subject: Re: [dts] [PATCH V1] conf/supportlist: add more support nics for IPv6_in_IPv4_tunnel
Date: Tue, 29 Jan 2019 03:19:39 +0000 [thread overview]
Message-ID: <E08767FB2CE10642B6780736EAC070F604906600@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1548400897-36304-1-git-send-email-bingx.y.yao@intel.com>
Tested-by : Zhu, WenhuiX <wenhuix.zhu@intel.com>
-----Original Message-----
From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of yaobing
Sent: Friday, January 25, 2019 3:22 PM
To: dts@dpdk.org
Cc: Yao, BingX Y <bingx.y.yao@intel.com>
Subject: [dts] [PATCH V1] conf/supportlist: add more support nics for IPv6_in_IPv4_tunnel
add more support nics to IPv6_in_IPv4_tunnel
Signed-off-by: yaobing <bingx.y.yao@intel.com>
---
conf/test_case_supportlist.json | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/conf/test_case_supportlist.json b/conf/test_case_supportlist.json index 571bb5c..ced96e0 100644
--- a/conf/test_case_supportlist.json
+++ b/conf/test_case_supportlist.json
@@ -167,13 +167,17 @@
"NIC": [
"powerville",
"niantic",
- "fortville_25g"
+ "fortville_25g",
+ "fortville_eagle",
+ "fortville_spirit",
+ "fortville_spirit_single",
+ "fortpark_TLV"
],
"Target": [
"ALL"
],
"Bug ID": "",
- "Comments": "IPv6_in_IPv4 tunnel packet detect only support on Niantic and i350"
+ "Comments": "IPv6_in_IPv4 tunnel packet detect only support on Niantic/FVL/powerville/fortpark_TLV"
}
],
"IP_in_IPv6_tunnel": [
--
2.17.2
next prev parent reply other threads:[~2019-01-29 3:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 7:21 yaobing
2019-01-29 3:19 ` Zhu, WenhuiX [this message]
2019-01-30 6:18 ` 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=E08767FB2CE10642B6780736EAC070F604906600@shsmsx102.ccr.corp.intel.com \
--to=wenhuix.zhu@intel.com \
--cc=bingx.y.yao@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).