linux-next: Tree for Sep 16

2020-09-16 Thread Stephen Rothwell
Hi all, Changes since 20200915: New tree: s390-setfs The akpm-current tree gained a conflict against the dma-mapping tree. Non-merge commits (relative to Linus' tree): 7322 8259 files changed, 258836 insertions(+), 146908 deletions(-) --

Re: linux-next: Tree for Sep 16 (kernel/sched/core.c)

2019-09-24 Thread Randy Dunlap
On 9/18/19 3:03 AM, Patrick Bellasi wrote: > > On Wed, Sep 18, 2019 at 07:05:53 +0100, Ingo Molnar wrote... > >> * Randy Dunlap wrote: >> >>> On 9/17/19 6:38 AM, Patrick Bellasi wrote: On Tue, Sep 17, 2019 at 08:52:42 +0100, Ingo Molnar wrote... > * Randy Dunlap wrote: >

Re: linux-next: Tree for Sep 16 (kernel/sched/core.c)

2019-09-18 Thread Patrick Bellasi
On Wed, Sep 18, 2019 at 07:05:53 +0100, Ingo Molnar wrote... > * Randy Dunlap wrote: > >> On 9/17/19 6:38 AM, Patrick Bellasi wrote: >> > >> > On Tue, Sep 17, 2019 at 08:52:42 +0100, Ingo Molnar wrote... >> > >> >> * Randy Dunlap wrote: >> >> >> >>> On 9/16/19 3:38 PM, Mark Brown wrote: >> >

Re: linux-next: Tree for Sep 16 (kernel/sched/core.c)

2019-09-17 Thread Ingo Molnar
* Randy Dunlap wrote: > On 9/17/19 6:38 AM, Patrick Bellasi wrote: > > > > On Tue, Sep 17, 2019 at 08:52:42 +0100, Ingo Molnar wrote... > > > >> * Randy Dunlap wrote: > >> > >>> On 9/16/19 3:38 PM, Mark Brown wrote: > Hi all, > > Changes since 20190915: > > >>> > >>> on x

Re: linux-next: Tree for Sep 16 (kernel/sched/core.c)

2019-09-17 Thread Randy Dunlap
On 9/17/19 6:38 AM, Patrick Bellasi wrote: > > On Tue, Sep 17, 2019 at 08:52:42 +0100, Ingo Molnar wrote... > >> * Randy Dunlap wrote: >> >>> On 9/16/19 3:38 PM, Mark Brown wrote: Hi all, Changes since 20190915: >>> >>> on x86_64: >>> >>> when CONFIG_CGROUPS is not set: > >

Re: linux-next: Tree for Sep 16 (kernel/sched/core.c)

2019-09-17 Thread Randy Dunlap
On 9/17/19 6:50 AM, Patrick Bellasi wrote: > > On Tue, Sep 17, 2019 at 14:38:28 +0100, Patrick Bellasi wrote... > >> On Tue, Sep 17, 2019 at 08:52:42 +0100, Ingo Molnar wrote... >> >>> * Randy Dunlap wrote: >>> On 9/16/19 3:38 PM, Mark Brown wrote: > Hi all, > > Changes since 20

Re: linux-next: Tree for Sep 16 (kernel/sched/core.c)

2019-09-17 Thread Patrick Bellasi
On Tue, Sep 17, 2019 at 08:52:42 +0100, Ingo Molnar wrote... > * Randy Dunlap wrote: > >> On 9/16/19 3:38 PM, Mark Brown wrote: >> > Hi all, >> > >> > Changes since 20190915: >> > >> >> on x86_64: >> >> when CONFIG_CGROUPS is not set: Hi Randy, thanks for the report. >> CC kernel/s

Re: linux-next: Tree for Sep 16 (kernel/sched/core.c)

2019-09-17 Thread Ingo Molnar
* Randy Dunlap wrote: > On 9/16/19 3:38 PM, Mark Brown wrote: > > Hi all, > > > > Changes since 20190915: > > > > on x86_64: > > when CONFIG_CGROUPS is not set: > > CC kernel/sched/core.o > ../kernel/sched/core.c: In function ‘uclamp_update_active_tasks’: > ../kernel/sched/core.c:10

Re: linux-next: Tree for Sep 16 (kernel/sched/core.c)

2019-09-16 Thread Randy Dunlap
On 9/16/19 3:38 PM, Mark Brown wrote: > Hi all, > > Changes since 20190915: > on x86_64: when CONFIG_CGROUPS is not set: CC kernel/sched/core.o ../kernel/sched/core.c: In function ‘uclamp_update_active_tasks’: ../kernel/sched/core.c:1081:23: error: storage size of ‘it’ isn’t known str

linux-next: Tree for Sep 16

2019-09-16 Thread Mark Brown
Hi all, Changes since 20190915: The arm64 tree acquired a conflict with the compiler-attributes tree. The ia64 tree acquired a conflict with the dma-mapping tree. The vfs tree acquired a conflict with the ubifds tree. A workaround was applied for a merge issue between the drm and kbuild trees

Re: linux-next: Tree for Sep 16 (spi/spi-bcm-qspi.c)

2016-09-16 Thread Randy Dunlap
On 09/15/16 21:45, Stephen Rothwell wrote: > Hi all, > > Changes since 20160915: > on i386: when CONFIG_PM_SLEEP and CONFIG_SUSPEND are not enabled: ../drivers/spi/spi-bcm-qspi.c:1300:13: error: 'bcm_qspi_suspend' undeclared here (not in a function) .suspend = bcm_qspi_suspend,

linux-next: Tree for Sep 16

2016-09-15 Thread Stephen Rothwell
Hi all, Changes since 20160915: New tree: kgdb The kbuild tree still had its build failure and warnings for PowerPC, for which I applied a couple of patches The drm-intel tree gained a conflict against Linus' tree. The drm-msm tree gained a conflict against Linus' tree. The block tree gained

linux-next: Tree for Sep 16

2015-09-15 Thread Stephen Rothwell
Hi all, Changes since 20150915: Dropped tree: akpm-current (build conflict) I used the h8300 tree from next-20150828 since the current tree has been rebased onto something very old :-( The net-next tree gained a build failure for which I applied a fix patch. The bluetooth tree still had its bu

Re: linux-next: Tree for Sep 16

2014-09-17 Thread Guenter Roeck
On Tue, Sep 16, 2014 at 05:56:12PM +1000, Stephen Rothwell wrote: > Hi all, > > Changes since 20140912: > > The net tree gained a build failure so I used the version from > next-20140915. > > The nfs tree lost its build failure. > > The v4l-dvb tree still had its build failure so I used the ver

linux-next: Tree for Sep 16

2014-09-16 Thread Stephen Rothwell
Hi all, Changes since 20140912: The net tree gained a build failure so I used the version from next-20140915. The nfs tree lost its build failure. The v4l-dvb tree still had its build failure so I used the version from next-20140908. The slave-dma tree gained a build faiure so I used the versi

linux-next: Tree for Sep 16

2013-09-15 Thread Stephen Rothwell
Hi all, Please do not add any code for v3.13 to your linux-next included branches until after v3.12-rc1 is released. Changes since 20130913: The h8300-remove tree gained a conflict against Linus' tree. The aio-direct tree gained a conflict against Linus' tree. -