[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1460943531.10638.99.camel@edumazet-glaptop3.roam.corp.google.com>
Date: Sun, 17 Apr 2016 18:38:51 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Craig Gallek <kraig@...gle.com>,
Eric Dumazet <edumazet@...gle.com>
Subject: Re: linux-next: manual merge of the net-next tree with the net tree
On Mon, 2016-04-18 at 11:31 +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the net-next tree got a conflict in:
>
> net/ipv4/udp.c
>
> between commit:
>
> d894ba18d4e4 ("soreuseport: fix ordering for mixed v4/v6 sockets")
>
> from the net tree and commit:
>
> ca065d0cf80f ("udp: no longer use SLAB_DESTROY_BY_RCU")
>
> from the net-next tree.
>
> I tried to fixed it up (see below). Unfortunately,
> hlist_add_tail_rcu() does not exist. So instead I have reverted commit
> d894ba18d4e4 ("soreuseport: fix ordering for mixed v4/v6 sockets") for
> today.
Hi Stephen
Craig warned that this would happen indeed, and provided a net-next
patch, to help David with this conflict.
https://patchwork.ozlabs.org/patch/611093/
Thanks
Powered by blists - more mailing lists