From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Shahaf Shuler <shahafs@mellanox.com>, Yongseok Koh <yskoh@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/7] net/mlx5: fixes for the new flow engine
Date: Tue, 9 Oct 2018 16:49:20 +0100 [thread overview]
Message-ID: <83c2d9cd-4775-fbcb-7d7d-ed7b37cdd509@intel.com> (raw)
In-Reply-To: <VI1PR05MB44319A62ADE9E53FF1537E75C3E70@VI1PR05MB4431.eurprd05.prod.outlook.com>
On 10/9/2018 9:58 AM, Shahaf Shuler wrote:
> Monday, October 8, 2018 9:02 PM, Yongseok Koh:
>> Subject: [PATCH 0/7] net/mlx5: fixes for the new flow engine
>>
>> Minor fixes accumulated since the following two patchsets.
>>
>> net/mlx5: add Direct Verbs flow driver support [1]
>> net/mlx5: migrate Linux TC flower driver to new flow engine
>>
>> [1] http://patches.dpdk.org/cover/45248
>> [2] http://patches.dpdk.org/cover/44897
>>
>> Yongseok Koh (7):
>> net/mlx5: fix wrong flow action macro usage
>> net/mlx5: use standard IP protocol numbers
>> net/mlx5: rename flow macros
>> net/mlx5: fix validation of VLAN ID in flow spec
>> net/mlx5: fix flow validation for no fate action
>> net/mlx5: add missing VLAN action constraints
>> net/mlx5: fix errno values for flow engine
>>
>> drivers/net/mlx5/mlx5_flow.c | 117 +++++++++++++++++++---------------
>> ---
>> drivers/net/mlx5/mlx5_flow.h | 54 ++++++++---------
>> drivers/net/mlx5/mlx5_flow_dv.c | 30 +++++-----
>> drivers/net/mlx5/mlx5_flow_tcf.c | 78 +++++++++++++++++++------
>> drivers/net/mlx5/mlx5_flow_verbs.c | 59 ++++++++++---------
>> 5 files changed, 193 insertions(+), 145 deletions(-)
>
> Series applied to next-net-mlx, thanks.
> Need to add the missing VLAN limitation of the "pop always to non-uplink" on a separate commit, don't want to stall the entire series.
Hi Shahaf,
These are fixing mlx5 patches which are merged very recently, that is why I
tried to squash these to original commit. This is both for more clean git
history and to have correct Fixes information in commit logs.
I can able to squash: 1/7, 2/7 & 4/7
But 4 are still remaining, main reason is they fixes more than one commit so not
easy to squash into one.
I won't merge remaining ones for now, can you please rebase them on top of
next-net, and try to arrange in a way to squash into next-net, if not able to
make we can get them as it is.
next prev parent reply other threads:[~2018-10-09 15:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 18:02 Yongseok Koh
2018-10-08 18:02 ` [dpdk-dev] [PATCH 1/7] net/mlx5: fix wrong flow action macro usage Yongseok Koh
2018-10-09 7:45 ` Ori Kam
2018-10-08 18:02 ` [dpdk-dev] [PATCH 2/7] net/mlx5: use standard IP protocol numbers Yongseok Koh
2018-10-09 7:37 ` Ori Kam
2018-10-09 8:02 ` Yongseok Koh
2018-10-09 15:39 ` Ferruh Yigit
2018-10-08 18:02 ` [dpdk-dev] [PATCH 3/7] net/mlx5: rename flow macros Yongseok Koh
2018-10-09 7:43 ` Ori Kam
2018-10-09 8:05 ` Yongseok Koh
2018-10-09 8:17 ` Yongseok Koh
2018-10-10 11:57 ` Ferruh Yigit
2018-10-08 18:02 ` [dpdk-dev] [PATCH 4/7] net/mlx5: fix validation of VLAN ID in flow spec Yongseok Koh
2018-10-09 7:47 ` Ori Kam
2018-10-09 15:44 ` Ferruh Yigit
2018-10-08 18:02 ` [dpdk-dev] [PATCH 5/7] net/mlx5: fix flow validation for no fate action Yongseok Koh
2018-10-09 7:49 ` Ori Kam
2018-10-10 12:24 ` Ferruh Yigit
2018-10-08 18:02 ` [dpdk-dev] [PATCH 6/7] net/mlx5: add missing VLAN action constraints Yongseok Koh
2018-10-08 19:48 ` Or Gerlitz
2018-10-08 18:02 ` [dpdk-dev] [PATCH 7/7] net/mlx5: fix errno values for flow engine Yongseok Koh
2018-10-09 7:53 ` Ori Kam
2018-10-10 12:59 ` Ferruh Yigit
2018-10-09 8:58 ` [dpdk-dev] [PATCH 0/7] net/mlx5: fixes for the new " Shahaf Shuler
2018-10-09 15:49 ` Ferruh Yigit [this message]
2018-10-10 5:57 ` Shahaf Shuler
2018-10-10 10:57 ` Ferruh Yigit
2018-10-10 13:01 ` Ferruh Yigit
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=83c2d9cd-4775-fbcb-7d7d-ed7b37cdd509@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=shahafs@mellanox.com \
--cc=yskoh@mellanox.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).