From: <nareddy@marvell.com>
To: <dts@dpdk.org>
Cc: <fmasood@marvell.com>, <avijay@marvell.com>,
Praneeth Reddy <nareddy@marvell.com>
Subject: [dts] [PATCH] TestSuite_link_flowctrl.py: pause_frame_fwd is not supported for cavium_a064
Date: Fri, 9 Aug 2019 09:59:48 +0530 [thread overview]
Message-ID: <1565324988-4100-1-git-send-email-nareddy@marvell.com> (raw)
From: Praneeth Reddy <nareddy@marvell.com>
removed pause_frame_fwd parameter and also disabled verifying packets for cavium_a064
Signed-off-by: Praneeth Reddy <nareddy@marvell.com>
---
tests/TestSuite_link_flowctrl.py | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/tests/TestSuite_link_flowctrl.py b/tests/TestSuite_link_flowctrl.py
index 841951f..4229aa4 100644
--- a/tests/TestSuite_link_flowctrl.py
+++ b/tests/TestSuite_link_flowctrl.py
@@ -168,7 +168,7 @@ class TestLinkFlowctrl(TestCase):
tgenInput = []
tgenInput.append((tester_tx_port, tester_rx_port, "test.pcap"))
- if (self.nic in ["cavium_a063"]):
+ if (self.nic in ["cavium_a063", "cavium_a064"]):
self.dut.send_expect("set flow_ctrl rx %s tx %s 300 50 10 1 autoneg %s %d " % (
flow_control,
flow_control,
@@ -277,7 +277,7 @@ class TestLinkFlowctrl(TestCase):
PAUSE Frames must not be received by testpmd
"""
- if (self.nic in ["cavium_a063"]):
+ if (self.nic in ["cavium_a063", "cavium_a064"]):
pause_frames = [self.build_pause_frame(0),
self.build_pause_frame(1)]
else:
@@ -296,7 +296,7 @@ class TestLinkFlowctrl(TestCase):
PAUSE Frames must not be received by testpmd
"""
- if (self.nic in ["cavium_a063"]):
+ if (self.nic in ["cavium_a063", "cavium_a064"]):
pause_frames = [self.build_pause_frame(0),
self.build_pause_frame(1)]
else:
--
1.8.3.1
next reply other threads:[~2019-08-09 4:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 4:29 nareddy [this message]
2019-08-12 6:53 ` 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=1565324988-4100-1-git-send-email-nareddy@marvell.com \
--to=nareddy@marvell.com \
--cc=avijay@marvell.com \
--cc=dts@dpdk.org \
--cc=fmasood@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).