[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190207183620.7h4i4fdl4g7kgkjz@salvia>
Date: Thu, 7 Feb 2019 19:36:20 +0100
From: Pablo Neira Ayuso <pablo@...filter.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: David Miller <davem@...emloft.net>,
Networking <netdev@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Guy Shattah <sguy@...lanox.com>,
Saeed Mahameed <saeedm@...lanox.com>
Subject: Re: linux-next: manual merge of the net-next tree with the net tree
Hi Stephen,
On Thu, Feb 07, 2019 at 11:54:24AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the net-next tree got a conflict in:
>
> drivers/net/ethernet/mellanox/mlx5/core/en_tc.c
>
> between commit:
>
> 1651925d403e ("net/mlx5e: Use the inner headers to determine tc/pedit offload limitation on decap flows")
>
> from the net tree and commit:
>
> 738678817573 ("drivers: net: use flow action infrastructure")
>
> from the net-next tree.
This conflict resolution when merging net into net-next looks good to me.
Thanks.
Powered by blists - more mailing lists