linux-next: Tree for Apr 8

2021-04-08 Thread Stephen Rothwell
Hi all, Changes since 20210407: The net-next tree gained conflicts against the net and bpf trees. The bluetooth tree gained a build failure so I used the version from next-20210407. The irqchip tree gained a build failure so I used the version from next-20210407. The akpm-current tree gained

Re: linux-next: Tree for Apr 8 (iio/adc/)

2019-04-15 Thread Fabrice Gasnier
On 4/14/19 2:30 PM, Jonathan Cameron wrote: > On Mon, 8 Apr 2019 09:09:37 -0700 > Randy Dunlap wrote: > >> On 4/7/19 10:41 PM, Stephen Rothwell wrote: >>> Hi all, >>> >>> Changes since 20190405: >>> >> >> on i386 or x86_64: >> >> modular: >> ERROR: "is_stm32_timer_trigger"

Re: linux-next: Tree for Apr 8 (iio/adc/)

2019-04-14 Thread Jonathan Cameron
On Mon, 8 Apr 2019 09:09:37 -0700 Randy Dunlap wrote: > On 4/7/19 10:41 PM, Stephen Rothwell wrote: > > Hi all, > > > > Changes since 20190405: > > > > on i386 or x86_64: > > modular: > ERROR: "is_stm32_timer_trigger" [drivers/iio/adc/stm32-dfsdm-adc.ko] > undefined! > > or builtin: >

Re: linux-next: Tree for Apr 8 (iio/adc/)

2019-04-08 Thread Randy Dunlap
On 4/7/19 10:41 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20190405: > on i386 or x86_64: modular: ERROR: "is_stm32_timer_trigger" [drivers/iio/adc/stm32-dfsdm-adc.ko] undefined! or builtin: ld: drivers/iio/adc/stm32-dfsdm-adc.o: in function `stm32_dfsdm_postenable':

linux-next: Tree for Apr 8

2019-04-07 Thread Stephen Rothwell
Hi all, Changes since 20190405: The kspp-gustavo tree gained a conflict against Linus' tree. The drm tree inherited the build failure from the drm-misc tree for which I disabled a driver. The audit tree gained a conflict against Linus' tree. The staging tree gained a conflict against the

linux-next: Tree for Apr 8

2016-04-07 Thread Stephen Rothwell
Hi all, Changes since 20160407: The akpm-current tree still had its build failure for which I applied a patch. Non-merge commits (relative to Linus' tree): 3002 2806 files changed, 114490 insertions(+), 69528 deletions(-)

linux-next: Tree for Apr 8

2016-04-07 Thread Stephen Rothwell
Hi all, Changes since 20160407: The akpm-current tree still had its build failure for which I applied a patch. Non-merge commits (relative to Linus' tree): 3002 2806 files changed, 114490 insertions(+), 69528 deletions(-)

linux-next: Tree for Apr 8

2015-04-08 Thread Stephen Rothwell
Hi all, Changes since 20150407: The arm-soc tree still had its build failure for which I reverted a commit. The spi tree lost its build failure. The tip tree's build failure was a semantic merge conflict so I applied a supplied fix. The akpm-current tree gained conflicts against the tip tree.

linux-next: Tree for Apr 8

2015-04-08 Thread Stephen Rothwell
Hi all, Changes since 20150407: The arm-soc tree still had its build failure for which I reverted a commit. The spi tree lost its build failure. The tip tree's build failure was a semantic merge conflict so I applied a supplied fix. The akpm-current tree gained conflicts against the tip tree.

linux-next: Tree for Apr 8

2014-04-07 Thread Stephen Rothwell
Hi all, Please do not add material intended for v3.16 to your linux-next included branches until after v3.15-rc1 is released. This tree still fails (more than usual) the powerpc allyesconfig build. Changes since 20140407: Dropped trees: akpm-current, akpm (too complex conflicts) The powerpc

linux-next: Tree for Apr 8

2014-04-07 Thread Stephen Rothwell
Hi all, Please do not add material intended for v3.16 to your linux-next included branches until after v3.15-rc1 is released. This tree still fails (more than usual) the powerpc allyesconfig build. Changes since 20140407: Dropped trees: akpm-current, akpm (too complex conflicts) The powerpc

Re: linux-next: Tree for Apr 8

2013-04-10 Thread Stephen Rothwell
Hi Geert, On Wed, 10 Apr 2013 10:51:54 +0200 Geert Uytterhoeven wrote: > > make: /opt/cross/gcc-4.6-nolibc/bin/alpha-linux-gcc: Command not found Fixed. Sorry about that. -- Cheers, Stephen Rothwells...@canb.auug.org.au pgpgJhF43W2eW.pgp Description: PGP signature

Re: linux-next: Tree for Apr 8

2013-04-10 Thread Geert Uytterhoeven
make: /opt/cross/gcc-4.6-nolibc/bin/alpha-linux-gcc: Command not found Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm

Re: linux-next: Tree for Apr 8

2013-04-10 Thread Geert Uytterhoeven
make: /opt/cross/gcc-4.6-nolibc/bin/alpha-linux-gcc: Command not found Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm

Re: linux-next: Tree for Apr 8

2013-04-10 Thread Stephen Rothwell
Hi Geert, On Wed, 10 Apr 2013 10:51:54 +0200 Geert Uytterhoeven ge...@linux-m68k.org wrote: make: /opt/cross/gcc-4.6-nolibc/bin/alpha-linux-gcc: Command not found Fixed. Sorry about that. -- Cheers, Stephen Rothwells...@canb.auug.org.au pgpgJhF43W2eW.pgp Description:

linux-next: Tree for Apr 8

2013-04-08 Thread Stephen Rothwell
Hi all, Changes since 20130405: The vfs tree gained a build failure so I used the version from next-20130405. The wireless-next tree still had its build failure for which I applied a supplied patch. The mfd tree gained a build failure so I used the version from next-20130405. The omap_dss2

linux-next: Tree for Apr 8

2013-04-08 Thread Stephen Rothwell
Hi all, Changes since 20130405: The vfs tree gained a build failure so I used the version from next-20130405. The wireless-next tree still had its build failure for which I applied a supplied patch. The mfd tree gained a build failure so I used the version from next-20130405. The omap_dss2