From: "Ma, LihongX" <lihongx.ma@intel.com>
To: "Zhu, ShuaiX" <shuaix.zhu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Zhu, ShuaiX" <shuaix.zhu@intel.com>
Subject: Re: [dts] [PATCH V1] tests/vhost_virtio_user_interrupt:fix test case blocked issue
Date: Thu, 24 Oct 2019 05:08:42 +0000 [thread overview]
Message-ID: <BE1E572D0441E34284F1F8B7AC28F1970BB175D5@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1571889680-133888-1-git-send-email-shuaix.zhu@intel.com>
Hi, shuai
Can you put the dpdk commit it in this patch ?
-----Original Message-----
From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of zhu,shuai
Sent: Thursday, October 24, 2019 12:01 PM
To: dts@dpdk.org
Cc: Zhu, ShuaiX <shuaix.zhu@intel.com>
Subject: [dts] [PATCH V1] tests/vhost_virtio_user_interrupt:fix test case blocked issue
Modify the code due to dpdk changes.
Signed-off-by: zhu,shuai <shuaix.zhu@intel.com>
---
tests/TestSuite_vhost_virtio_user_interrupt.py | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/tests/TestSuite_vhost_virtio_user_interrupt.py b/tests/TestSuite_vhost_virtio_user_interrupt.py
index 5422e04..91edcce 100644
--- a/tests/TestSuite_vhost_virtio_user_interrupt.py
+++ b/tests/TestSuite_vhost_virtio_user_interrupt.py
@@ -84,6 +84,10 @@ class TestVirtioUserInterrupt(TestCase):
self.dut.send_expect("cp ./examples/l3fwd-power/main.c .", "#")
self.dut.send_expect(
"sed -i '/DEV_RX_OFFLOAD_CHECKSUM/d' ./examples/l3fwd-power/main.c", "#", 10)
+ self.dut.send_expect(
+ "sed -i '/if (promiscuous_on/i\#if 0' ./examples/l3fwd-power/main.c", "#", 10)
+ self.dut.send_expect(
+ "sed -i '/rte_spinlock_init(&(locks/i\#endif' ./examples/l3fwd-power/main.c", "#", 10)
out = self.dut.build_dpdk_apps("./examples/l3fwd-power")
self.verify("Error" not in out, "compilation l3fwd-power error")
--
2.17.2
prev parent reply other threads:[~2019-10-24 5:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 4:01 zhu,shuai
2019-10-24 5:01 ` Zhu, WenhuiX
2019-10-24 5:08 ` Ma, LihongX [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=BE1E572D0441E34284F1F8B7AC28F1970BB175D5@SHSMSX101.ccr.corp.intel.com \
--to=lihongx.ma@intel.com \
--cc=dts@dpdk.org \
--cc=shuaix.zhu@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).