From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: 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>,
"arybchenko@solarflare.com" <arybchenko@solarflare.com>,
Shahaf Shuler <shahafs@mellanox.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH v2 1/2] app/testpmd: fix metadata API and Tx insertion
Date: Thu, 25 Oct 2018 13:32:07 +0200 [thread overview]
Message-ID: <2211689.3Us0HrgFnG@xps> (raw)
In-Reply-To: <64b69095-279e-1698-a7ca-7fbbb36ee067@intel.com>
25/10/2018 12:45, Ferruh Yigit:
> On 10/24/2018 11:49 AM, Ori Kam wrote:
> > From: dev <dev-bounces@dpdk.org> On Behalf Of Dekel Peled
> >>
> >> 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?
OK, no problem
next prev parent reply other threads:[~2018-10-25 11:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 13:28 [PATCH 1/2] app/testpmd: fix metadata API and Tx insertion Dekel Peled
2018-10-23 13:28 ` [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 ` [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
2018-10-25 11:32 ` Thomas Monjalon [this message]
2018-10-24 6:22 ` [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=2211689.3Us0HrgFnG@xps \
--to=thomas@monjalon.net \
--cc=adrien.mazarguil@6wind.com \
--cc=arybchenko@solarflare.com \
--cc=bernard.iremonger@intel.com \
--cc=dekelp@mellanox.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jingjing.wu@intel.com \
--cc=olivier.matz@6wind.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.