[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <wihsh9lmoor.fsf@dev-r-vrt-156.mtr.labs.mlnx>
Date: Wed, 28 Feb 2018 11:46:44 +0200
From: Petr Machata <petrm@...lanox.com>
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>,
Thomas Winter <Thomas.Winter@...iedtelesis.co.nz>,
Jiri Pirko <jiri@...lanox.com>,
Ido Schimmel <idosch@...lanox.com>
Subject: Re: linux-next: manual merge of the net-next tree with the net tree
Stephen Rothwell <sfr@...b.auug.org.au> writes:
> Today's linux-next merge of the net-next tree got a conflict in:
>
> net/ipv4/ip_tunnel.c
>
> between commit:
>
> 4e994776e7bd ("ip_tunnel: Do not use mark in skb by default")
>
> from the net tree and commit:
>
> b0066da52ea5 ("ip_tunnel: Rename & publish init_tunnel_flow")
>
> from the net-next tree.
>
> I fixed it up (see below) and can carry the fix as necessary.
Looks good, thanks!
Petr
Powered by blists - more mailing lists