From: "Ma, LihongX" <lihongx.ma@intel.com>
To: "Tu, Lijuan" <lijuan.tu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V1] tests/ipfrag: add RTE prefix to ipv4 route
Date: Thu, 27 Jun 2019 01:56:50 +0000 [thread overview]
Message-ID: <BE1E572D0441E34284F1F8B7AC28F1970BACEBCE@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <8CE3E05A3F976642AAB0F4675D0AD20E0BAC5301@SHSMSX101.ccr.corp.intel.com>
hi, lijuan
I have upstream the patch of V2.
Thanks.
-----Original Message-----
From: Tu, Lijuan
Sent: Wednesday, June 26, 2019 4:37 PM
To: Ma, LihongX <lihongx.ma@intel.com>; dts@dpdk.org
Cc: Ma, LihongX <lihongx.ma@intel.com>
Subject: RE: [dts] [PATCH V1] tests/ipfrag: add RTE prefix to ipv4 route
Could you please rework your patch?
Applying: tests/ipfrag: add RTE prefix to ipv4 route
error: patch failed: tests/TestSuite_ipfrag.py:42
error: tests/TestSuite_ipfrag.py: patch does not apply
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of lihong
> Sent: Wednesday, June 19, 2019 7:41 AM
> To: dts@dpdk.org
> Cc: Ma, LihongX <lihongx.ma@intel.com>
> Subject: [dts] [PATCH V1] tests/ipfrag: add RTE prefix to ipv4 route
>
> As dpdk commit 24ac604ef7469eb5773 and 0c9da7555da8c8373, add RTE
> prefix to ipv4 route struct.
>
> Signed-off-by: lihong <lihongx.ma@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..a75fff2 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.7.4
prev parent reply other threads:[~2019-06-27 1:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 23:41 lihong
2019-06-19 7:20 ` Zhu, ShuaiX
2019-06-26 8:36 ` Tu, Lijuan
2019-06-27 1:56 ` 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=BE1E572D0441E34284F1F8B7AC28F1970BACEBCE@SHSMSX101.ccr.corp.intel.com \
--to=lihongx.ma@intel.com \
--cc=dts@dpdk.org \
--cc=lijuan.tu@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).