From: "xu,gang" <gangx.xu@intel.com>
To: dts@dpdk.org
Cc: "xu,gang" <gangx.xu@intel.com>
Subject: [dts] [PATCH V1] fix NIC binding error
Date: Fri, 18 Nov 2016 10:59:28 +0800 [thread overview]
Message-ID: <1479437968-4538-4-git-send-email-gangx.xu@intel.com> (raw)
In-Reply-To: <1479437968-4538-1-git-send-email-gangx.xu@intel.com>
remove dead code and open test link status interrupt port available
Signed-off-by: xu,gang <gangx.xu@intel.com>
---
tests/TestSuite_link_status_interrupt.py | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/tests/TestSuite_link_status_interrupt.py b/tests/TestSuite_link_status_interrupt.py
index b00fa88..c50a99d 100644
--- a/tests/TestSuite_link_status_interrupt.py
+++ b/tests/TestSuite_link_status_interrupt.py
@@ -109,7 +109,6 @@ class TestLinkStatusInterrupt(TestCase):
self.dut.send_expect("rmmod igb_uio", "# ")
self.dut.send_expect(
"insmod %s/kmod/igb_uio.ko %s" % (self.target, intr_mode[n]), "# ")
- self.dut.send_expect("tools/dpdk-devbind.py --bind=igb_uio 03:00.0 03:00.1", "# ")
out = self.dut.send_expect(
"dmesg -c | grep '\<%s\>'" % (intr_mode_output[n]), "# ")
self.verify(
@@ -125,7 +124,7 @@ class TestLinkStatusInterrupt(TestCase):
self.set_link_status_and_verify(testPorts[1], 'up')
self.dut.send_expect("^C", "# ")
- def FAILING_test_link_status_interrupt_port_available(self):
+ def test_link_status_interrupt_port_available(self):
"""
Port available.
"""
--
1.9.3
next prev parent reply other threads:[~2016-11-18 2:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 2:59 [dts] [PATCH V1] add test suite ip_pipekine config file xu,gang
2016-11-18 2:59 ` [dts] [PATCH V1] add test suite l2fwd-jobstats xu,gang
2016-11-18 3:18 ` Liu, Yong
2016-11-18 2:59 ` [dts] [PATCH V1] add test suite packet ordering xu,gang
2016-11-18 2:59 ` xu,gang [this message]
2016-11-23 2:00 ` [dts] [PATCH V1] fix NIC binding error Liu, Yong
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=1479437968-4538-4-git-send-email-gangx.xu@intel.com \
--to=gangx.xu@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).