From: "Wu, ChangqingX" <changqingx.wu@intel.com>
To: "Lin, Xueqin" <xueqin.lin@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Lin, Xueqin" <xueqin.lin@intel.com>
Subject: Re: [dts] [PATCH] tests/hotplug_mp: fix hotplug_mp example build path issue
Date: Fri, 7 Dec 2018 08:38:37 +0000 [thread overview]
Message-ID: <7F81DD3887C58F49A6B2EFEC3C28E22E0B67A97A@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1544148354-108179-1-git-send-email-xueqin.lin@intel.com>
Subject: [dts] [PATCH] tests/hotplug_mp: fix hotplug_mp example build path issue
From: "xueqin.lin" <xueqin.lin@intel.com>
Signed-off-by: Xueqin Lin <xueqin.lin@intel.com>
Tested-by: Changqing Wu <changqingx.wu@intel.com>
-----Original Message-----
From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Xueqin Lin
Sent: Friday, December 7, 2018 10:06 AM
To: dts@dpdk.org
Cc: Lin, Xueqin <xueqin.lin@intel.com>
Subject: [dts] [PATCH] tests/hotplug_mp: fix hotplug_mp example build path issue
From: "xueqin.lin" <xueqin.lin@intel.com>
Signed-off-by: Xueqin Lin <xueqin.lin@intel.com>
---
tests/TestSuite_hotplug_mp.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/TestSuite_hotplug_mp.py b/tests/TestSuite_hotplug_mp.py index 20f914a..ff89164 100644
--- a/tests/TestSuite_hotplug_mp.py
+++ b/tests/TestSuite_hotplug_mp.py
@@ -22,7 +22,7 @@ class TestHotplugMp(TestCase):
self.verify(len(self.dut_ports) >= 1, "Insufficient ports")
self.intf0 = self.dut.ports_info[0]['intf']
self.pci0 = self.dut.ports_info[0]['pci']
- out = self.dut.build_dpdk_apps("./examples/multi_process/hotplug_mp")
+ out = self.dut.build_dpdk_apps("./examples/multi_process/")
self.verify('Error' not in out, "Compilation failed")
# Start one new session to run primary process
self.session_pri = self.dut.new_session()
--
2.7.5
next prev parent reply other threads:[~2018-12-07 8:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 2:05 Xueqin Lin
2018-12-07 8:23 ` Wu, ChangqingX
2018-12-07 8:38 ` Wu, ChangqingX [this message]
2018-12-11 10:37 ` 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=7F81DD3887C58F49A6B2EFEC3C28E22E0B67A97A@SHSMSX101.ccr.corp.intel.com \
--to=changqingx.wu@intel.com \
--cc=dts@dpdk.org \
--cc=xueqin.lin@intel.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).