From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH 0/7] net/mlx5: fixes for the new flow engine Date: Tue, 9 Oct 2018 16:49:20 +0100 Message-ID: <83c2d9cd-4775-fbcb-7d7d-ed7b37cdd509@intel.com> References: <20181008180150.39273-1-yskoh@mellanox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: "dev@dpdk.org" To: Shahaf Shuler , Yongseok Koh Return-path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 0AE4C1B5A9 for ; Tue, 9 Oct 2018 17:49:57 +0200 (CEST) In-Reply-To: Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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.