Hi Nelio,
On 6/21/2017 2:02 PM, Nélio Laranjeiro wrote:
> On Wed, Jun 21, 2017 at 11:55:58AM +0000, Shachar Beiser wrote:
>> Missing room in flow allocation to store the drop specification.
>> Changing flow without storing the change in rte_flow.
>> Fixes: 88c77dedfbb0 ("net/mlx5: implement drop action in hardware
>> classifier")
>>
>> Signed-off-by: Shachar Beiser <[email protected]>
<...>
>> --
>> 1.8.3.1
>
> Acked-by: Nelio Laranjeiro <[email protected]>
>
> Ferruh, this patch is fixing an issue of a patch only present in your
> master-net branch, the fixline sha1 will be wrong.
I can squash this into relevant patch (88c77dedfbb0).
But there is another patch [1] that cause conflict and seems fixing same
commit (88c77dedfbb0) again.
What do you think squashing all three into one?
I can share latest patch if you want.
[1] net/mlx5: fix creation of drop flows
http://dpdk.org/browse/next/dpdk-next-net/commit/?id=e0e37c1f80a00a2acbb581649b3125a5d465f2c6
>
> Thanks,
>
