[dts] [PATCH V2] test_plans/uni_pkt:Modify the naming of the NIC.

[Yao, BingX Y]

Tested-by: yaobing <bingx.y.yao at intel.com>

-----Original Message-----
From: dts [mailto:dts-bounces at dpdk.org] On Behalf Of zhu,shuai
Sent: Friday, February 22, 2019 9:32 AM
To: dts at dpdk.org
Cc: Zhu, ShuaiX <shuaix.zhu at intel.com>
Subject: [dts] [PATCH V2] test_plans/uni_pkt:Modify the naming of the NIC.

Modify the naming of the NIC in combination with the case.

Signed-off-by: zhu,shuai <shuaix.zhu at intel.com>
---
 test_plans/uni_pkt_test_plan.rst | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/test_plans/uni_pkt_test_plan.rst b/test_plans/uni_pkt_test_plan.rst
index 905e27a..a87e373 100644
--- a/test_plans/uni_pkt_test_plan.rst
+++ b/test_plans/uni_pkt_test_plan.rst
@@ -51,7 +51,7 @@ Enable ABI and disable vector ixgbe driver in dpdk configuration file.
 Plug in three different types of nic on the board.
 1x Intel® XL710-DA2 (Eagle Fountain)
 1x Intel® 82599 Gigabit Ethernet Controller -1x Intel® I350 Gigabit Network Connection
+1x Intel® powerville Gigabit Network Connection
 
 Start testpmd and then enable rxonly and verbose mode::
 
@@ -95,7 +95,7 @@ Test Case: IPv4&L4 packet type detect
 
 This case checked that whether L3 and L4 packet can be normally detected.
 Only Fortville can detect icmp packet.
-Only niantic and i350 can detect ipv4 extension packet.
+Only niantic and powerville can detect ipv4 extension packet.
 Fortville did not detect whether packet contain ipv4 header options, so L3  type will be shown as IPV4_EXT_UNKNOWN.
 Fortville will identify all unrecognized L4 packet as L4_NONFRAG.
@@ -141,14 +141,14 @@ Send IP fragment+TCP packet and verify L2/L3/L4 corrected(Fortville)::
     (outer) L3 type: IPV4_EXT_UNKNOWN
     (outer) L4 type: L4_FRAG
 
-Send IP extension packet and verify L2/L3 corrected(Niantic,i350)::
+Send IP extension packet and verify L2/L3 corrected(Niantic,powerville)::
 
     sendp([Ether()/IP(ihl=10)/Raw('\0'*40)],iface=txItf)
 
     (outer) L3 type: IPV4_EXT
     (outer) L4 type: Unknown
 
-Send IP extension+SCTP packet and verify L2/L3/L4 corrected(Niantic,i350)::
+Send IP extension+SCTP packet and verify L2/L3/L4 corrected(Niantic,powerville)::
 
     sendp([Ether()/IP(ihl=10)/SCTP()/Raw('\0'*40)],iface=txItf)
 
@@ -191,7 +191,7 @@ Send IPv6 fragment packet and verify L2/L3/L4 corrected(Fortville)::
     (outer) L3 type: IPV6_EXT_UNKNOWN
     (outer) L4 type: L4_FRAG
 
-Send IPv6 fragment packet and verify L2/L3/L4 corrected(Niantic,i350)::
+Send IPv6 fragment packet and verify L2/L3/L4 corrected(Niantic,powerville)::
 
     sendp([Ether()/IPv6()/IPv6ExtHdrFragment()/Raw('\0'*60)],iface=txItf)
 
@@ -283,11 +283,11 @@ Send IPv4+IPv6+ICMP packet and verify inner and outer L2/L3/L4 corrected::
 
     Inner L4 type: ICMP
 
-Test Case: IPv6 in IPv4 tunnel packet type detect by niantic and i350 -=====================================================================
+Test Case: IPv6 in IPv4 tunnel packet type detect 
+================================================
 
 This case checked that whether IPv4 in IPv6 tunnel packet can be normally -detected by Niantic and i350.
+detected.
 
 Send IPv4+IPv6 packet and verify inner and outer L2/L3/L4 corrected::
 
--
2.17.2