From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Ma, LihongX" <lihongx.ma@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Zhang, YanX A" <yanx.a.zhang@intel.com>,
"Ma, LihongX" <lihongx.ma@intel.com>
Subject: Re: [dts] [PATCH V2] tests/vf_daemon: add rte prefix to ether structures
Date: Thu, 27 Jun 2019 03:25:19 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BAC5916@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1559268660-4748-1-git-send-email-lihongx.ma@intel.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of lihong
> Sent: Friday, May 31, 2019 10:11 AM
> To: dts@dpdk.org
> Cc: Zhang, YanX A <yanx.a.zhang@intel.com>; Ma, LihongX
> <lihongx.ma@intel.com>
> Subject: [dts] [PATCH V2] tests/vf_daemon: add rte prefix to ether structures
>
> As dpdk commit: 6d13ea8e8e49ab9, add 'rte_' prefix to structures
> ether_addr; so change our code related it.
>
> Signed-off-by: lihong <lihongx.ma@intel.com>
> ---
> tests/TestSuite_vf_daemon.py | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/tests/TestSuite_vf_daemon.py b/tests/TestSuite_vf_daemon.py
> index 2d5c59f..cc55f65 100644
> --- a/tests/TestSuite_vf_daemon.py
> +++ b/tests/TestSuite_vf_daemon.py
> @@ -487,10 +487,10 @@ class TestVfDaemon(TestCase):
> fake_mac = '00:11:22:33:44:55'
> time.sleep(5)
> self.vm0_dut.send_expect("sed -i -e '/int r;/a " +\
> - "\ struct ether_addr fake_mac = {.addr_bytes = {0x00, 0x11, 0x22,
> 0x33, 0x44, 0x55},};'" +\
> + "\ struct rte_ether_addr fake_mac = {.addr_bytes = {0x00, 0x11,
> 0x22, 0x33, 0x44, 0x55},};'" +\
> " app/test-pmd/macswap_sse.h", "# ", 30)
> line_num = self.vm0_dut.send_expect("sed -n '/_mm_storeu_si128/='
> app/test-pmd/macswap_sse.h |sed -n 5p", "# ",30)
> - self.vm0_dut.send_expect("sed -i -e '%sa\ether_addr_copy(&fake_mac,
> ð_hdr[0]->s_addr);'" % str(line_num)+\
> + self.vm0_dut.send_expect("sed -i -e
> + '%sa\\rte_ether_addr_copy(&fake_mac, ð_hdr[0]->s_addr);'" %
> + str(line_num)+\
> " app/test-pmd/macswap_sse.h", "# ", 30)
> time.sleep(3)
>
> @@ -525,7 +525,7 @@ class TestVfDaemon(TestCase):
>
> self.vm0_testpmd.quit()
> self.dut_testpmd.quit()
> - self.vm0_dut.send_expect("sed -i '/struct ether_addr fake_mac =
> {.addr_bytes = " +\
> + self.vm0_dut.send_expect("sed -i '/struct rte_ether_addr
> + fake_mac = {.addr_bytes = " +\
> "{0x00, 0x11, 0x22, 0x33, 0x44, 0x55},};/d' app/test-
> pmd/macswap_sse.h", "# ", 30)
> self.vm0_dut.send_expect("sed -i '%sd'" % line_num +\
> " app/test-pmd/macswap_sse.h", "# ", 30)
> --
> 2.7.4
prev parent reply other threads:[~2019-06-27 3:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 2:11 lihong
2019-06-27 3:25 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BAC5916@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=lihongx.ma@intel.com \
--cc=yanx.a.zhang@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).