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>,
	"olivier.matz@6wind.com" <olivier.matz@6wind.com>,
	Adrien Mazarguil <adrien.mazarguil@6wind.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	"arybchenko@solarflare.com" <arybchenko@solarflare.com>
Cc: Shahaf Shuler <shahafs@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 1/2] app/testpmd: fix metadata API and Tx insertion
Date: Thu, 25 Oct 2018 11:45:44 +0100	[thread overview]
Message-ID: <64b69095-279e-1698-a7ca-7fbbb36ee067@intel.com> (raw)
In-Reply-To: <VI1PR05MB34403C2C616227AD6C1F5EDCDBF60@VI1PR05MB3440.eurprd05.prod.outlook.com>

On 10/24/2018 11:49 AM, Ori Kam wrote:
> 
> 
>> -----Original Message-----
>> From: dev <dev-bounces@dpdk.org> On Behalf Of Dekel Peled
>> Sent: Wednesday, October 24, 2018 9:22 AM
>> To: wenzhuo.lu@intel.com; jingjing.wu@intel.com;
>> bernard.iremonger@intel.com; olivier.matz@6wind.com; Adrien Mazarguil
>> <adrien.mazarguil@6wind.com>; Thomas Monjalon <thomas@monjalon.net>;
>> ferruh.yigit@intel.com; arybchenko@solarflare.com
>> Cc: Shahaf Shuler <shahafs@mellanox.com>; dev@dpdk.org; Ori Kam
>> <orika@mellanox.com>; Dekel Peled <dekelp@mellanox.com>
>> Subject: [dpdk-dev] [PATCH v2 1/2] app/testpmd: fix metadata API and Tx
>> insertion
>>
>> Previous patch introduces the Tx metadata feature, with unnecessary
>> restrictions on data entry.
>> It also used the metadata in txonly fwd engine only.
>>
>> This fix removes the data entry restrictions on metadata item.
>> It also implements callback function to add the metadata in every
>> Tx packet, sent by any fwd engine.
>>
>> Fixes: 32eef22f0b79 ("app/testpmd: support metadata as flow rule item")
>> Cc: dekelp@mellanox.com
>>
>> ---
>> v2:
>> No change in this patch.
>> Modified other patch in series.
>> ---
>>
>> Signed-off-by: Dekel Peled <dekelp@mellanox.com>
<...>
> Acked-by: Ori Kam <orika@mellanox.com>

Series applied to dpdk-next-net/master, thanks.


Thomas,
Since the patches has been fixed are in next-net, the Fixes tags will be wrong
when you pull, can you please fix them while merging?

Thanks.

  reply	other threads:[~2018-10-25 10:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-23 13:28 [dpdk-dev] [PATCH " Dekel Peled
2018-10-23 13:28 ` [dpdk-dev] [PATCH 2/2] ethdev: fix metadata documentation Dekel Peled
2018-10-23 18:05   ` Ori Kam
2018-10-24  5:54     ` Dekel Peled
2018-10-24  6:21 ` [dpdk-dev] [PATCH v2 1/2] app/testpmd: fix metadata API and Tx insertion Dekel Peled
2018-10-24 10:49   ` Ori Kam
2018-10-25 10:45     ` Ferruh Yigit [this message]
2018-10-25 11:32       ` Thomas Monjalon
2018-10-24  6:22 ` [dpdk-dev] [PATCH v2 2/2] ethdev: fix metadata documentation Dekel Peled
2018-10-24 10:43   ` Ori Kam

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=64b69095-279e-1698-a7ca-7fbbb36ee067@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=arybchenko@solarflare.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dekelp@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=olivier.matz@6wind.com \
    --cc=orika@mellanox.com \
    --cc=shahafs@mellanox.com \
    --cc=thomas@monjalon.net \
    --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).