From: "Ma, LihongX" <lihongx.ma@intel.com>
To: "Li, WenjieX A" <wenjiex.a.li@intel.com>,
"Zhu, WenhuiX" <wenhuix.zhu@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: "Zhu, WenhuiX" <wenhuix.zhu@intel.com>
Subject: Re: [dts] [PATCH V1] tests:align directory changes in dpdk
Date: Fri, 24 May 2019 09:17:44 +0000 [thread overview]
Message-ID: <BE1E572D0441E34284F1F8B7AC28F1970BAAF72C@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <8688172CD5C0B74590FAE19D9579F94B536F3D41@SHSMSX103.ccr.corp.intel.com>
Reviewed-by: lihong<lihongx.ma@intel.com>
-----Original Message-----
From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Li, WenjieX A
Sent: Friday, May 24, 2019 4:03 PM
To: Zhu, WenhuiX <wenhuix.zhu@intel.com>; dts@dpdk.org
Cc: Zhu, WenhuiX <wenhuix.zhu@intel.com>
Subject: Re: [dts] [PATCH V1] tests:align directory changes in dpdk
Reviewed-by: Wenjie <wenjiex.a.li@intel.com>
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of zhuwenhui
> Sent: Friday, May 24, 2019 4:03 PM
> To: dts@dpdk.org
> Cc: Zhu, WenhuiX <wenhuix.zhu@intel.com>
> Subject: [dts] [PATCH V1] tests:align directory changes in dpdk
>
> According to the change of dpdk commit id "218c4e68c1d9".
> Changed from "common_linuxapp" to "common_linux"
>
> Signed-off-by: zhuwenhui <wenhuix.zhu@intel.com>
> ---
> tests/TestSuite_ftag.py | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tests/TestSuite_ftag.py b/tests/TestSuite_ftag.py index
> e58a57a..9d30918 100644
> --- a/tests/TestSuite_ftag.py
> +++ b/tests/TestSuite_ftag.py
> @@ -70,7 +70,7 @@ class TestFtag(TestCase):
> patch_dst = "/tmp/"
> self.dut.session.copy_file_to(patch_file, patch_dst)
> self.patch_hotfix_dpdk(patch_dst +
> "fm10k-add-a-unit-test-for-FTAG- based-forwarding.patch", True)
> - self.dut.send_expect("sed -i -e
> '/CONFIG_RTE_VIRTIO_USER=y/a\CONFIG_RTE_LIBRTE_FM10K_FTAG_FWD
> =y' config/common_linuxapp", "# ")
> + self.dut.send_expect("sed -i -e
> +
> '/CONFIG_RTE_VIRTIO_USER=y/a\CONFIG_RTE_LIBRTE_FM10K_FTAG_FWD
> =y'
> + config/common_linux", "# ")
> self.dut.send_expect("sed -i -e '/SRCS-y +=
> test_pmd_perf.c/a\SRCS-y
> += test_fm10k_ftag.c' app/test/Makefile", "# ")
> self.dut.build_install_dpdk(self.dut.target)
>
> @@ -165,7 +165,7 @@ class TestFtag(TestCase):
> Run after each test suite.
> """
> self.dut.kill_all()
> - self.dut.send_expect("sed -i
> '/CONFIG_RTE_LIBRTE_FM10K_FTAG_FWD=y/d' config/common_linuxapp", "# ")
> + self.dut.send_expect("sed -i
> + '/CONFIG_RTE_LIBRTE_FM10K_FTAG_FWD=y/d' config/common_linux",
> "# ")
> self.dut.send_expect("sed -i '/SRCS-y += test_fm10k_ftag.c/d'
> app/test/Makefile", "# ")
> patch_dst = "/tmp/"
> self.patch_hotfix_dpdk(patch_dst +
> "fm10k-add-a-unit-test-for-FTAG- based-forwarding.patch", False)
> --
> 2.17.2
next prev parent reply other threads:[~2019-05-24 9:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 8:02 zhuwenhui
2019-05-24 8:03 ` Li, WenjieX A
2019-05-24 9:17 ` Ma, LihongX [this message]
2019-05-29 2:35 ` 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=BE1E572D0441E34284F1F8B7AC28F1970BAAF72C@SHSMSX101.ccr.corp.intel.com \
--to=lihongx.ma@intel.com \
--cc=dts@dpdk.org \
--cc=wenhuix.zhu@intel.com \
--cc=wenjiex.a.li@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).