From: "Wu, ChangqingX" <changqingx.wu@intel.com>
To: "dts@dpdk.org" <dts@dpdk.org>, "Tu, Lijuan" <lijuan.tu@intel.com>
Cc: "Li, WenjieX A" <wenjiex.a.li@intel.com>,
"Zhu, ShuaiX" <shuaix.zhu@intel.com>
Subject: Re: [dts] [PATCH V1] tests/ipfrag: align the change in DPDK
Date: Wed, 19 Jun 2019 05:44:11 +0000 [thread overview]
Message-ID: <7F81DD3887C58F49A6B2EFEC3C28E22E0B70EC3A@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <4DC48DF9BDA3E54A836D2D3C057DEC6F0B197AFE@SHSMSX101.ccr.corp.intel.com>
Hi,
Would you help to merge this patch, it has a greater impact on our daily result
Thanks.
changqingx
-----Original Message-----
From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Zhu, ShuaiX
Sent: Monday, June 10, 2019 9:48 AM
To: Li, WenjieX A <wenjiex.a.li@intel.com>; dts@dpdk.org
Cc: Li, WenjieX A <wenjiex.a.li@intel.com>; Zhu, ShuaiX <shuaix.zhu@intel.com>
Subject: Re: [dts] [PATCH V1] tests/ipfrag: align the change in DPDK
Testde-by: Zhu, ShuaiX <shuaix.zhu@intel.com>
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Wenjie Li
> Sent: Thursday, May 30, 2019 12:44 PM
> To: dts@dpdk.org
> Cc: Li, WenjieX A <wenjiex.a.li@intel.com>
> Subject: [dts] [PATCH V1] tests/ipfrag: align the change in DPDK
>
> From: "Wenjie Li" <wenjiex.a.li@intel.com>
>
> align changes in dpdk a7c528e5d71ff3f56:
> "
> net: add rte prefix to IP structure
> Add 'rte_' prefix to structures:
> - rename struct ipv4_hdr as struct rte_ipv4_hdr.
> - rename struct ipv6_hdr as struct rte_ipv6_hdr.
> "
>
> Signed-off-by: Wenjie Li <wenjiex.a.li@intel.com>
> ---
> tests/TestSuite_ipfrag.py | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/tests/TestSuite_ipfrag.py b/tests/TestSuite_ipfrag.py
> index 38a27e9..c148d2a 100644
> --- a/tests/TestSuite_ipfrag.py
> +++ b/tests/TestSuite_ipfrag.py
> @@ -42,14 +42,14 @@ from settings import HEADER_SIZE from packet
> import Packet
>
> lpm_table_ipv4 = [
> - "{IPv4(100,10,0,0), 16, P1}",
> - "{IPv4(100,20,0,0), 16, P1}",
> - "{IPv4(100,30,0,0), 16, P0}",
> - "{IPv4(100,40,0,0), 16, P0}",
> - "{IPv4(100,50,0,0), 16, P1}",
> - "{IPv4(100,60,0,0), 16, P1}",
> - "{IPv4(100,70,0,0), 16, P0}",
> - "{IPv4(100,80,0,0), 16, P0}",
> + "{RTE_IPv4(100,10,0,0), 16, P1}",
> + "{RTE_IPv4(100,20,0,0), 16, P1}",
> + "{RTE_IPv4(100,30,0,0), 16, P0}",
> + "{RTE_IPv4(100,40,0,0), 16, P0}",
> + "{RTE_IPv4(100,50,0,0), 16, P1}",
> + "{RTE_IPv4(100,60,0,0), 16, P1}",
> + "{RTE_IPv4(100,70,0,0), 16, P0}",
> + "{RTE_IPv4(100,80,0,0), 16, P0}",
> ]
>
> lpm_table_ipv6 = [
> --
> 2.17.2
prev parent reply other threads:[~2019-06-19 5:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 4:43 Wenjie Li
2019-06-10 1:47 ` Zhu, ShuaiX
2019-06-19 5:44 ` Wu, ChangqingX [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=7F81DD3887C58F49A6B2EFEC3C28E22E0B70EC3A@SHSMSX101.ccr.corp.intel.com \
--to=changqingx.wu@intel.com \
--cc=dts@dpdk.org \
--cc=lijuan.tu@intel.com \
--cc=shuaix.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).