test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: Phanendra Vukkisala <pvukkisala@marvell.com>,
	"dts@dpdk.org" <dts@dpdk.org>
Cc: Vijaya Bhaskar Annayyolla <avijay@marvell.com>,
	Faisal Masood <fmasood@marvell.com>
Subject: Re: [dts] [PATCH] tests/TestSuite_uni_pkt: Run supported cases on	cavium device
Date: Mon, 7 Jan 2019 08:45:18 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0B9FDF83@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1546580462-18745-1-git-send-email-pvukkisala@marvell.com>

Applied, thanks

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Phanendra Vukkisala
> Sent: Friday, January 4, 2019 1:42 PM
> To: dts@dpdk.org
> Cc: Vijaya Bhaskar Annayyolla <avijay@marvell.com>; Faisal Masood
> <fmasood@marvell.com>; Phanendra Vukkisala <pvukkisala@marvell.com>
> Subject: [dts] [PATCH] tests/TestSuite_uni_pkt: Run supported cases on
> cavium device
> 
> From: pvukkisala <pvukkisala@marvell.com>
> 
> Few tests in unified packet suite are supported by cavium device, did
> required changes to run those test cases.
> 
> Signed-off-by: phanendra,vukkisala <pvukkisala@marvell.com>
> ---
>  tests/TestSuite_uni_pkt.py |    8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/tests/TestSuite_uni_pkt.py b/tests/TestSuite_uni_pkt.py index
> f2d0f83..17de58f 100644
> --- a/tests/TestSuite_uni_pkt.py
> +++ b/tests/TestSuite_uni_pkt.py
> @@ -118,7 +118,7 @@ class TestUniPacket(TestCase):
>          if "fortville" in self.nic or "fortpark_TLV" in self.nic:
>              outerL4Type = "L4_NONFRAG"
>              ipv4_default_packet_type = ["L2_ETHER",
> "L3_IPV4_EXT_UNKNOWN"]
> -        elif "niantic" in self.nic.lower() or "i350" in self.nic.lower():
> +        elif "niantic" in self.nic.lower() or "i350" in self.nic.lower() or
> "cavium" in self.nic.lower():
>              outerL4Type = ""
>              ipv4_default_packet_type = ["L2_ETHER", "L3_IPV4"]
>          pktType = {
> @@ -136,7 +136,7 @@ class TestUniPacket(TestCase):
>          if "fortville" in self.nic or "fortpark_TLV" in self.nic:
>              pktType.pop("MAC_IPihl_PKT")
>              pktType.pop("MAC_IPihl_SCTP_PKT")
> -        elif "niantic" in self.nic.lower() or "i350" in self.nic.lower():
> +        elif "niantic" in self.nic.lower() or "i350" in self.nic.lower() or
> "cavium" in self.nic.lower():
>              pktType.pop("MAC_IP_ICMP_PKT")
>              pktType.pop("MAC_IPFRAG_TCP_PKT")
> 
> @@ -149,7 +149,7 @@ class TestUniPacket(TestCase):
>          if "fortville" in self.nic or "fortpark_TLV" in self.nic:
>              outerL4Type = "L4_NONFRAG"
>              ipv6_default_packet_type = ["L2_ETHER",
> "L3_IPV6_EXT_UNKNOWN"]
> -        elif "niantic" in self.nic.lower() or "i350" in self.nic.lower():
> +        elif "niantic" in self.nic.lower() or "i350" in self.nic.lower() or
> "cavium" in self.nic.lower():
>              outerL4Type = ""
>              ipv6_default_packet_type = ["L2_ETHER", "L3_IPV6"]
> 
> @@ -164,7 +164,7 @@ class TestUniPacket(TestCase):
>          # delete the unsupported packet based on nic type
>          if "fortville" in self.nic or "fortpark_TLV" in self.nic:
>              pktType.pop("MAC_IPv6FRAG_PKT_N")
> -        elif "niantic" in self.nic.lower() or "i350" in self.nic.lower():
> +        elif "niantic" in self.nic.lower() or "i350" in self.nic.lower() or
> "cavium" in self.nic.lower():
>              pktType.pop("MAC_IPv6FRAG_PKT_F")
> 
>          self.run_test(pktType)
> --
> 1.7.9.5

      reply	other threads:[~2019-01-07  8:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-04  5:42 Phanendra Vukkisala
2019-01-07  8:45 ` Tu, Lijuan [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=8CE3E05A3F976642AAB0F4675D0AD20E0B9FDF83@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=avijay@marvell.com \
    --cc=dts@dpdk.org \
    --cc=fmasood@marvell.com \
    --cc=pvukkisala@marvell.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).