linux-next: Tree for Dec 22

2020-12-21 Thread Stephen Rothwell
Hi all, News: there will be no linux-next releases between Dec 24 and Jan 3 inclusive. Please do not add any v5.12 destined code to your linux-next included branches until after v5.11-rc1 has been released. Changes since 20201221: The device-mapper tree gained a conflict against Linus' tree.

linux-next: Tree for Dec 22

2017-12-21 Thread Stephen Rothwell
Hi all, News: The next release will be on January 2nd. Changes since 20171221: New tree: mips (the old mips tree has been renamed to mips-james) The aspeed tree gained conflicts against the arm-soc tree. The omap tree gained a conflict against the keystone tree. The xfs tree gained a

linux-next: Tree for Dec 22

2017-12-21 Thread Stephen Rothwell
Hi all, News: The next release will be on January 2nd. Changes since 20171221: New tree: mips (the old mips tree has been renamed to mips-james) The aspeed tree gained conflicts against the arm-soc tree. The omap tree gained a conflict against the keystone tree. The xfs tree gained a

linux-next: Tree for Dec 22

2016-12-21 Thread Stephen Rothwell
Hi all, Please do not add any material for v4.11 to your linux-next included branches until after v4.10-rc1 has been released. There will be no linux-next releases from me between Dec 24 and Jan 2 inclusive (unless I get really bored with my new toys :-)). Changes since 20161221: Non-merge

linux-next: Tree for Dec 22

2016-12-21 Thread Stephen Rothwell
Hi all, Please do not add any material for v4.11 to your linux-next included branches until after v4.10-rc1 has been released. There will be no linux-next releases from me between Dec 24 and Jan 2 inclusive (unless I get really bored with my new toys :-)). Changes since 20161221: Non-merge

Re: linux-next: Tree for Dec 22 (mm/memcontrol)

2015-12-22 Thread Randy Dunlap
On 12/22/15 11:19, Andrew Morton wrote: > On Tue, 22 Dec 2015 10:15:37 -0800 Randy Dunlap wrote: > >> On 12/21/15 21:29, Stephen Rothwell wrote: >>> Hi all, >>> >>> Changes since 20151221: >>> >> >> on i386 or x86_64: >> >> when CONFIG_SLOB=y: >> >> ../mm/memcontrol.c: In function

Re: linux-next: Tree for Dec 22 (mm/memcontrol)

2015-12-22 Thread Andrew Morton
On Tue, 22 Dec 2015 10:15:37 -0800 Randy Dunlap wrote: > On 12/21/15 21:29, Stephen Rothwell wrote: > > Hi all, > > > > Changes since 20151221: > > > > on i386 or x86_64: > > when CONFIG_SLOB=y: > > ../mm/memcontrol.c: In function 'memcg_update_kmem_limit': > ../mm/memcontrol.c:2974:3:

Re: linux-next: Tree for Dec 22 (mm/memcontrol)

2015-12-22 Thread Randy Dunlap
On 12/21/15 21:29, Stephen Rothwell wrote: > Hi all, > > Changes since 20151221: > on i386 or x86_64: when CONFIG_SLOB=y: ../mm/memcontrol.c: In function 'memcg_update_kmem_limit': ../mm/memcontrol.c:2974:3: error: implicit declaration of function 'memcg_online_kmem'

Re: linux-next: Tree for Dec 22 (mm/memcontrol)

2015-12-22 Thread Randy Dunlap
On 12/21/15 21:29, Stephen Rothwell wrote: > Hi all, > > Changes since 20151221: > on i386 or x86_64: when CONFIG_SLOB=y: ../mm/memcontrol.c: In function 'memcg_update_kmem_limit': ../mm/memcontrol.c:2974:3: error: implicit declaration of function 'memcg_online_kmem'

Re: linux-next: Tree for Dec 22 (mm/memcontrol)

2015-12-22 Thread Randy Dunlap
On 12/22/15 11:19, Andrew Morton wrote: > On Tue, 22 Dec 2015 10:15:37 -0800 Randy Dunlap wrote: > >> On 12/21/15 21:29, Stephen Rothwell wrote: >>> Hi all, >>> >>> Changes since 20151221: >>> >> >> on i386 or x86_64: >> >> when CONFIG_SLOB=y: >> >> ../mm/memcontrol.c: In

Re: linux-next: Tree for Dec 22 (mm/memcontrol)

2015-12-22 Thread Andrew Morton
On Tue, 22 Dec 2015 10:15:37 -0800 Randy Dunlap wrote: > On 12/21/15 21:29, Stephen Rothwell wrote: > > Hi all, > > > > Changes since 20151221: > > > > on i386 or x86_64: > > when CONFIG_SLOB=y: > > ../mm/memcontrol.c: In function 'memcg_update_kmem_limit': >

Re: linux-next: Tree for Dec 22

2015-12-21 Thread Sudip Mukherjee
On Tue, Dec 22, 2015 at 04:29:55PM +1100, Stephen Rothwell wrote: > Hi all, > > Changes since 20151221: cris allmodconfig fails with: ../block/partitions/ldm.c: In function 'ldm_partition': ../block/partitions/ldm.c:1567:1: internal compiler error: in gen_reg_rtx, at emit-rtl.c:1027 compiler

linux-next: Tree for Dec 22

2015-12-21 Thread Stephen Rothwell
Hi all, Changes since 20151221: I added a patch to the orangefs tree for a post release discovered build failure. The i2c tree still had its build failure for which I applied a patch. The drm tree gained a conflict against the imx-mxs tree. The drm-intel tree gained a conflict against Linus'

linux-next: Tree for Dec 22

2015-12-21 Thread Stephen Rothwell
Hi all, Changes since 20151221: I added a patch to the orangefs tree for a post release discovered build failure. The i2c tree still had its build failure for which I applied a patch. The drm tree gained a conflict against the imx-mxs tree. The drm-intel tree gained a conflict against Linus'

Re: linux-next: Tree for Dec 22

2015-12-21 Thread Sudip Mukherjee
On Tue, Dec 22, 2015 at 04:29:55PM +1100, Stephen Rothwell wrote: > Hi all, > > Changes since 20151221: cris allmodconfig fails with: ../block/partitions/ldm.c: In function 'ldm_partition': ../block/partitions/ldm.c:1567:1: internal compiler error: in gen_reg_rtx, at emit-rtl.c:1027 compiler