linux-next: Tree for May 16

2019-05-15 Thread Stephen Rothwell
Hi all, Please do not add any v5.3 material to your linux-next included trees/branches until after v5.2-rc1 has been released. Changes since 20190515: The ftrace tree gained conflicts against Linus' tree. Non-merge commits (relative to Linus' tree): 1940 2029 files changed, 60303 insertions(+)

linux-next: Tree for May 16

2018-05-16 Thread Stephen Rothwell
Hi all, News: I will not be doing any linux-next releases between Friday 18 May and Friday 25 May inclusive. Changes since 20180515: New trees: samsung-krzk-fixes pinctrl-samsung-fixes The kbuild tree still had its build failure for which I applied a patch. The mips-james tree gained a

Re: linux-next: Tree for May 16 (net/core)

2017-05-16 Thread Eric Dumazet
On Tue, May 16, 2017 at 12:44 PM, Paul Gortmaker wrote: > On Tue, May 16, 2017 at 12:28 PM, Randy Dunlap wrote: >> On 05/15/17 18:21, Stephen Rothwell wrote: >>> Hi all, >>> >>> Changes since 20170515: >>> >> >> on i386 or x86_64: >> >> when CONFIG_INET is not enabled: >> >> ../net/core/sock.c: I

Re: linux-next: Tree for May 16 (net/core)

2017-05-16 Thread Paul Gortmaker
On Tue, May 16, 2017 at 12:28 PM, Randy Dunlap wrote: > On 05/15/17 18:21, Stephen Rothwell wrote: >> Hi all, >> >> Changes since 20170515: >> > > on i386 or x86_64: > > when CONFIG_INET is not enabled: > > ../net/core/sock.c: In function 'skb_orphan_partial': > ../net/core/sock.c:1810:2: error: i

Re: linux-next: Tree for May 16 (net/core)

2017-05-16 Thread Randy Dunlap
On 05/15/17 18:21, Stephen Rothwell wrote: > Hi all, > > Changes since 20170515: > on i386 or x86_64: when CONFIG_INET is not enabled: ../net/core/sock.c: In function 'skb_orphan_partial': ../net/core/sock.c:1810:2: error: implicit declaration of function 'skb_is_tcp_pure_ack' [-Werror=implic

linux-next: Tree for May 16

2017-05-15 Thread Stephen Rothwell
Hi all, Changes since 20170515: The akpm tree lost a patch that turned up elsewhere. Non-merge commits (relative to Linus' tree): 1064 1008 files changed, 26929 insertions(+), 14343 deletions(-) I have created today'

Re: linux-next: Tree for May 16

2016-05-15 Thread Stephen Rothwell
Hi all, I forgot to say: Please do not add any v4.8 destined material to your linux-next included branches until after v4.7-rc1 has been released. -- Cheers, Stephen Rothwell

linux-next: Tree for May 16

2016-05-15 Thread Stephen Rothwell
Hi all, Changes since 20160513: Undropped tree: rdma-leon The wireless-drivers-next tree gained a conflict aaginst the net-next tree. The rdma-leon tree lost its build failure. The spi tree gained a build failure so I used the version from next-20160513. The clk tree gained a conflict against

linux-next: Tree for May 16

2014-05-16 Thread Stephen Rothwell
Hi all, Changes since 20140515: My fixes tree contains: powerpc/ppc64: Allow allmodconfig to build (finally !) The gpio tree still had its build failure for which I reverted 2 commits. The net-next tree gained a conflict against the net tree. Non-merge commits (relative to Linus' tree)

linux-next: Tree for May 16

2013-05-15 Thread Stephen Rothwell
Hi all, Changes since 20130515: New tree: mvebu The renesas tree gained a conflict against Linus' tree. The akpm tree lost a patch that turned up elsewhere. I have created today's linux-next tree at git://git.kernel.