From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ori Kam <orika@mellanox.com>, Dekel Peled <dekelp@mellanox.com>,
"wenzhuo.lu@intel.com" <wenzhuo.lu@intel.com>,
"jingjing.wu@intel.com" <jingjing.wu@intel.com>,
"bernard.iremonger@intel.com" <bernard.iremonger@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Shahaf Shuler <shahafs@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v2] app/testpmd: fix MPLSoUDP encapsulation
Date: Tue, 11 Dec 2018 17:28:45 +0000 [thread overview]
Message-ID: <965c2eb3-4861-8723-cbf4-aaf011cb432a@intel.com> (raw)
In-Reply-To: <AM4PR05MB34258729B1743E1A082611B3DBA90@AM4PR05MB3425.eurprd05.prod.outlook.com>
On 12/6/2018 9:38 AM, Ori Kam wrote:
<...>
>>>> Subject: [dpdk-dev] [PATCH v2] app/testpmd: fix MPLSoUDP encapsulation
>>>>
>>>> In function cmd_set_mplsoudp_encap_parsed(), MPLS label value was set
>>>> in mplsoudp_encap_conf struct without the required offset.
>>>> As a result the value was copied incorrectly into rte_flow_item_mpls
>>>> struct.
>>>>
>>>> This patch sets MPLS label value in appropriate location at
>>>> mplsoudp_encap_conf struct, so it is correctly copied to
>>>> rte_flow_item_mpls struct.
>>>>
>>>> Fixes: a1191d39cb57 ("app/testpmd: add MPLSoUDP encapsulation")
>>>> Cc: orika@mellanox.com
>>>>
>>>> Signed-off-by: Dekel Peled <dekelp@mellanox.com>>
> Acked-by: Ori Kam <orika@mellanox.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-12-11 17:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 16:54 [dpdk-dev] [PATCH] " Dekel Peled
2018-11-20 8:23 ` Ori Kam
2018-11-21 15:19 ` Ferruh Yigit
2018-11-21 15:39 ` Ori Kam
2018-11-22 9:04 ` Adrien Mazarguil
2018-11-22 9:56 ` Dekel Peled
2018-11-22 10:14 ` Adrien Mazarguil
2018-11-22 16:18 ` Dekel Peled
2018-11-22 16:39 ` Ferruh Yigit
2018-12-04 13:51 ` [dpdk-dev] [PATCH v2] " Dekel Peled
2018-12-04 21:23 ` Ori Kam
2018-12-06 8:17 ` Dekel Peled
2018-12-06 9:38 ` Ori Kam
2018-12-11 17:28 ` Ferruh Yigit [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=965c2eb3-4861-8723-cbf4-aaf011cb432a@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dekelp@mellanox.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=orika@mellanox.com \
--cc=shahafs@mellanox.com \
--cc=wenzhuo.lu@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).