Re: linux-next: Tree for Oct 4 (net/rds/ib)

2019-10-04 Thread Randy Dunlap
On 10/3/19 10:59 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20191003: > on i386: ../net/rds/ib.c: In function ‘rds_ib_dev_free’: ../net/rds/ib.c:111:3: error: implicit declaration of function ‘dma_pool_destroy’; did you mean ‘mempool_destroy’? [-Werror=implicit-function-declarati

linux-next: Tree for Oct 4

2019-10-03 Thread Stephen Rothwell
Hi all, Changes since 20191003: My fixes tree contains: 04e6dac68d9b ("powerpc/64s/radix: fix for "tidy up TLB flushing code" and !CONFIG_PPC_RADIX_MMU") The hid tree gained a build failure so I used the version from next-20191003. The drm-misc tree gained a conflict against the admgpu tree

Re: linux-next: Tree for Oct 4

2018-10-04 Thread Guenter Roeck
On 10/04/2018 04:44 PM, Stephen Rothwell wrote: Hi Geert, On Thu, 4 Oct 2018 16:21:42 +0200 Geert Uytterhoeven wrote: On Thu, Oct 4, 2018 at 3:47 PM Guenter Roeck wrote: Time for a status report. Build results: total: 135 pass: 121 fail: 14 Failed builds: arm:allmodconfi

Re: linux-next: Tree for Oct 4

2018-10-04 Thread Stephen Rothwell
Hi Geert, On Thu, 4 Oct 2018 16:21:42 +0200 Geert Uytterhoeven wrote: > > On Thu, Oct 4, 2018 at 3:47 PM Guenter Roeck wrote: > > Time for a status report. > > > > Build results: > > total: 135 pass: 121 fail: 14 > > Failed builds: > > arm:allmodconfig > > i386:allyescon

Re: linux-next: Tree for Oct 4

2018-10-04 Thread Geert Uytterhoeven
On Thu, Oct 4, 2018 at 3:47 PM Guenter Roeck wrote: > Time for a status report. > > Build results: > total: 135 pass: 121 fail: 14 > Failed builds: > arm:allmodconfig > i386:allyesconfig > i386:allmodconfig > m68k:defconfig > m68k:allmodconfig >

Re: linux-next: Tree for Oct 4

2018-10-04 Thread Guenter Roeck
On Thu, Oct 04, 2018 at 06:34:49PM +1000, Stephen Rothwell wrote: > Hi all, > > Changes since 20181003: > > The bpf-next tree still had its build failure so I used the version > from next-20181002. > > The kvm-arm tree gained conflicts against the arm64 tree. > > The tty tree gained a build fai

linux-next: Tree for Oct 4

2018-10-04 Thread Stephen Rothwell
Hi all, Changes since 20181003: The bpf-next tree still had its build failure so I used the version from next-20181002. The kvm-arm tree gained conflicts against the arm64 tree. The tty tree gained a build failure so I used the version from next-20181003. The slave-dma tree gained a build fail

Re: linux-next: Tree for Oct 4

2016-10-03 Thread Stephen Rothwell
Hi all, On Tue, 4 Oct 2016 14:56:49 +1100 Stephen Rothwell wrote: > > There will be no linux-next release on Friday. > > Changes since 20161003: I forgot to say: Please do *not* add any v4.10 material to your linux-next included trees until v4.9-rc1 has been released i.e. the merge window clos

linux-next: Tree for Oct 4

2016-10-03 Thread Stephen Rothwell
Hi all, There will be no linux-next release on Friday. Changes since 20161003: Non-merge commits (relative to Linus' tree): 12964 9515 files changed, 516789 insertions(+), 294462 deletions(-) I have created today's l

Re: linux-next: Tree for Oct 4

2013-10-06 Thread Guenter Roeck
On 10/05/2013 03:44 PM, Mark Brown wrote: Hi all, Better late than never I've uploaded today's linux-next tree to the master branch of the repository below: git://gitorious.org/thierryreding/linux-next.git A next-20131004 tag is also provided for convenience. Each merge was tested wi

linux-next: Tree for Oct 4

2013-10-05 Thread Mark Brown
Hi all, Better late than never I've uploaded today's linux-next tree to the master branch of the repository below: git://gitorious.org/thierryreding/linux-next.git A next-20131004 tag is also provided for convenience. Each merge was tested with x86_664 allyesconfig. A few new conflicts