Re: linux-next: Tree for Sep 9 (drivers/usb/typec/mux/intel_pmc_mux.c)

2020-09-10 Thread Heikki Krogerus
On Wed, Sep 09, 2020 at 09:04:53AM -0700, Randy Dunlap wrote: > On 9/9/20 3:26 AM, Stephen Rothwell wrote: > > Hi all, > > > > Changes since 20200908: > > > > on x86_64: > > CC [M] drivers/usb/typec/mux/intel_pmc_mux.o > ../drivers/usb/typec/mux/intel_pmc_mux.c: In function ‘update_port_stat

Re: linux-next: Tree for Sep 9 (ath11k)

2020-09-10 Thread Kalle Valo
Kalle Valo writes: > Randy Dunlap writes: > >> On 9/9/20 3:26 AM, Stephen Rothwell wrote: >>> Hi all, >>> >>> Changes since 20200908: >>> >> >> on x86_64: >> >> ld: drivers/net/wireless/ath/ath11k/core.o: in function `ath11k_core_init': >> core.c:(.text+0x121f): undefined reference to `rproc_g

Re: linux-next: Tree for Sep 9 (ath11k)

2020-09-09 Thread Kalle Valo
Randy Dunlap writes: > On 9/9/20 3:26 AM, Stephen Rothwell wrote: >> Hi all, >> >> Changes since 20200908: >> > > on x86_64: > > ld: drivers/net/wireless/ath/ath11k/core.o: in function `ath11k_core_init': > core.c:(.text+0x121f): undefined reference to `rproc_get_by_phandle' This is because CO

linux-next: Tree for Sep 9

2020-09-09 Thread Stephen Rothwell
Hi all, Changes since 20200908: The v4l-dvb tree lost its build failure. The bpf-next tree still had its build failure so I used the version from next-20200903. The nand tree still had its build failure so I used the version from next-20200903. The tip tree lost its build failure. The rcu tre

linux-next: Tree for Sep 9

2016-09-08 Thread Stephen Rothwell
Hi all, Changes since 20160908: New tree: kvm-mips The btrfs-kdave tree still had its build failure so I used the version from next-20160906. The kbuild tree still had its build warnings for PowerPC, for which I reverted a commit. The devicetree tree gained a conflict against the imx-mxs tree.

linux-next: Tree for Sep 9

2015-09-08 Thread Stephen Rothwell
Hi all, Please do not add material for v4.4 until after v4.3-rc1 is out. Changes since 20150908: I used the h8300 tree from next-20150828 since the current tree has been rebased onto something very old :-( The drm-misc tree lost its build failure. The kvm tree gained a build failure for which

linux-next: Tree for Sep 9

2014-09-09 Thread Stephen Rothwell
Hi all, Changes since 20140908: New trees: kselftest-fixes and kselftest The v4l-dvb tree gained a build failure so I used the version from next-20140908. The wireless-next tree still had its build failure for which I applied a suggested fix patch. The drm tree still had its build failure for

Re: linux-next: Tree for Sep 9 (ntb)

2013-09-09 Thread Jon Mason
On Mon, Sep 09, 2013 at 11:12:51AM -0700, Randy Dunlap wrote: > On 09/08/13 23:16, Stephen Rothwell wrote: > > 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 20130906: > > > > > on x86_64: >

Re: linux-next: Tree for Sep 9 (ntb)

2013-09-09 Thread Randy Dunlap
On 09/08/13 23:16, Stephen Rothwell wrote: > 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 20130906: > on x86_64: drivers/built-in.o: In function `ntb_transport_free_queue': (.text+0x150344): undefi

linux-next: Tree for Sep 9

2013-09-08 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 20130906: The vfs tree gained a build failure so I used the version from next-20130906. The akpm tree gained conflicts against Linus' tree. ---