From: "Tu, Lijuan" <lijuan.tu@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 V2] tests/vdev_primary_secondary:Modify the matching data.
Date: Wed, 27 Nov 2019 09:30:51 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BB6976D@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1574820583-144415-1-git-send-email-shuaix.zhu@intel.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of zhu,shuai
> Sent: Wednesday, November 27, 2019 10:10 AM
> To: dts@dpdk.org
> Cc: Zhu, ShuaiX <shuaix.zhu@intel.com>
> Subject: [dts] [PATCH V2] tests/vdev_primary_secondary:Modify the
> matching data.
>
> Modify the matching data.
>
> Signed-off-by: zhu,shuai <shuaix.zhu@intel.com>
> ---
> tests/TestSuite_vdev_primary_secondary.py | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/tests/TestSuite_vdev_primary_secondary.py
> b/tests/TestSuite_vdev_primary_secondary.py
> index e03d615..9728985 100644
> --- a/tests/TestSuite_vdev_primary_secondary.py
> +++ b/tests/TestSuite_vdev_primary_secondary.py
> @@ -128,8 +128,7 @@ class TestVdevPrimarySecondary(TestCase):
> self.vm_dut.send_expect(
> "sed -i '/.offloads =
> DEV_RX_OFFLOAD_CHECKSUM,/d' ./examples/multi_process/symmetric_mp
> /main.c", "#")
> self.vm_dut.send_expect(
> - "sed -i 's/.mq_mode = ETH_MQ_RX_RSS,/.mq_mode =
> ETH_MQ_RX_NONE,/g' ./examples/multi_process/symmetric_mp/main.c",
> "#")
> - self.vm_dut.send_expect(
> + "sed -i
> 's/ETH_MQ_RX_RSS,/ETH_MQ_RX_NONE,/g' ./examples/multi_process/sym
> metric_mp/main.c", "#")
> out =
> self.vm_dut.build_dpdk_apps('./examples/multi_process/symmetric_mp')
> self.verify("Error" not in out, "compilation symmetric_mp error")
>
> --
> 2.17.2
prev parent reply other threads:[~2019-11-27 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 2:09 zhu,shuai
2019-11-27 9:30 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BB6976D@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@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).