DPDK patches and discussions
 help / color / mirror / Atom feed
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: Matan Azrad <matan@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] app/testpmd: enhance GTP support
Date: Mon, 6 Apr 2020 16:41:58 +0100	[thread overview]
Message-ID: <faa405e0-0e3a-0fc9-863a-207a5c414272@intel.com> (raw)
In-Reply-To: <AM6PR05MB5176303C3757C704B662F6D2DBCE0@AM6PR05MB5176.eurprd05.prod.outlook.com>

On 3/25/2020 8:27 AM, Ori Kam wrote:
> 
> 
>> -----Original Message-----
>> From: dev <dev-bounces@dpdk.org> On Behalf Of Dekel Peled
>> Sent: Wednesday, March 25, 2020 10:13 AM
>> To: Ori Kam <orika@mellanox.com>; wenzhuo.lu@intel.com;
>> jingjing.wu@intel.com; bernard.iremonger@intel.com
>> Cc: Matan Azrad <matan@mellanox.com>; dev@dpdk.org
>> Subject: [dpdk-dev] [PATCH v2] app/testpmd: enhance GTP support
>>
>> This patch adds CLI option to enter the v_pt_rsv_flags value for GTP
>> flow pattern item.
>> It also adds GTP as valid item in raw_encap and raw_decap setting.
>>
>> Signed-off-by: Dekel Peled <dekelp@mellanox.com>
> 
> Acked-by: Ori Kam <orika@mellanox.com>

Applied to dpdk-next-net/master, thanks.

      parent reply	other threads:[~2020-04-06 15:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-16  8:14 [dpdk-dev] [PATCH] " Dekel Peled
2020-03-24  9:58 ` Ori Kam
2020-03-24 12:39   ` Dekel Peled
2020-03-25  8:12 ` [dpdk-dev] [PATCH v2] " Dekel Peled
2020-03-25  8:27   ` Ori Kam
2020-03-29  9:20     ` Dekel Peled
2020-04-06 11:05       ` Dekel Peled
2020-04-06 11:16         ` Ferruh Yigit
2020-04-06 15:41     ` 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=faa405e0-0e3a-0fc9-863a-207a5c414272@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=matan@mellanox.com \
    --cc=orika@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).