Re: linux-next: Tree for May 30 (firmware_loader)

2019-05-30 Thread Matteo Croce
On May 31, 2019 2:06:46 AM GMT+02:00, Stephen Rothwell wrote: > Hi all, > > On Thu, 30 May 2019 09:10:13 -0700 Randy Dunlap > wrote: > > > > on i386 or x86_64: > > when CONFIG_PROC_SYSCTL is not set/enabled: > > > > ld: drivers/base/firmware_loader/fallback_table.o:(.data+0x1c): > undefined re

Re: linux-next: Tree for May 30 (firmware_loader)

2019-05-30 Thread Stephen Rothwell
Hi all, On Thu, 30 May 2019 09:10:13 -0700 Randy Dunlap wrote: > > on i386 or x86_64: > when CONFIG_PROC_SYSCTL is not set/enabled: > > ld: drivers/base/firmware_loader/fallback_table.o:(.data+0x1c): undefined > reference to `sysctl_vals' > ld: drivers/base/firmware_loader/fallback_table.o:(.da

Re: linux-next: Tree for May 30 (firmware_loader)

2019-05-30 Thread Randy Dunlap
On 5/29/19 11:21 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20190529: > on i386 or x86_64: when CONFIG_PROC_SYSCTL is not set/enabled: ld: drivers/base/firmware_loader/fallback_table.o:(.data+0x1c): undefined reference to `sysctl_vals' ld: drivers/base/firmware_loader/fallback_tab

linux-next: Tree for May 30

2019-05-29 Thread Stephen Rothwell
Hi all, Changes since 20190529: The net-next tree gained a conflict against the net tree. The userns tree gained a conflict against the arc-current tree. The akpm-current tree lost its build failure but gained another for which I applied a patch. It also gained a boot failure so I reverted 2 c

linux-next: Tree for May 30

2018-05-30 Thread Stephen Rothwell
Hi all, Changes since 20180529: New tree: cisco The drm-intel-fixes tree lost its build failure. The kbuild tree gained a build failure so I used the version from next-20180529. The dma-mapping tree gained a conflict against Linus' tree. The arm-soc tree gained a conflict against the arm tree

linux-next: Tree for May 30

2017-05-29 Thread Stephen Rothwell
Hi all, Changes since 20170529: New trees: reset, reset-fixes The nand tree gained a conflict against the jc_docs tree. Non-merge commits (relative to Linus' tree): 3099 3410 files changed, 126865 insertions(+), 68052 deletions(-) --

Re: linux-next: Tree for May 30

2016-05-30 Thread Sudip Mukherjee
On Monday 30 May 2016 08:52 AM, Stephen Rothwell wrote: Hi all, Changes since 20160527: Hi All, I have just built and booted with next-20160530 and my dmesg is full of warnings from ath9k. Last kernel tested was v4.6 and there was no problem with that. The traces are like: Call Trace: []

linux-next: Tree for May 30

2016-05-29 Thread Stephen Rothwell
Hi all, Changes since 20160527: My fixes tree is empty again. The akpm tree lost a patch that turned up elsewhere. Non-merge commits (relative to Linus' tree): 469 415 files changed, 11919 insertions(+), 4156 deletions(-) ---

linux-next: Tree for May 30

2014-05-30 Thread Stephen Rothwell
Hi all, The powerpc allyesconfig is again broken more than usual. Changes since 20140529: The mmc tree gained a build failure for which I reverted a commit. The omap_dss2 tree gained a conflict against the arm-soc tree. I added a couple of supplied patches to the tip tree. The tty tree lost i

Re: linux-next: Tree for May 30

2013-06-04 Thread Stephen Rothwell
Hi Nicolas, On Mon, 3 Jun 2013 10:45:15 +0200 Nicolas Ferre wrote: > > Is it possible for you to move the building to the replacement defconfigs: > at91sam9260_9g20_defconfig > at91sam9261_9g10_defconfig Done. -- Cheers, Stephen Rothwells...@canb.auug.org.au pgp_G__qS2WpD

Re: linux-next: Tree for May 30

2013-06-03 Thread Nicolas Ferre
On 03/06/2013 08:36, Stephen Rothwell : Hi Geert, On Thu, 30 May 2013 10:07:48 +0200 Geert Uytterhoeven wrote: The following defconfigs fail without anything useful in the log: - at91sam9g20_defconfig - at91sam9261_defconfig - at91sam9260_defconfig A manual run reveals why: Can't f

Re: linux-next: Tree for May 30

2013-06-02 Thread Stephen Rothwell
Hi Geert, On Thu, 30 May 2013 10:07:48 +0200 Geert Uytterhoeven wrote: > > The following defconfigs fail without anything useful in the log: > - at91sam9g20_defconfig > - at91sam9261_defconfig > - at91sam9260_defconfig > > A manual run reveals why: > Can't find default configuration "arch

Re: linux-next: Tree for May 30

2013-05-30 Thread Geert Uytterhoeven
On Thu, May 30, 2013 at 8:33 AM, Stephen Rothwell wrote: > Changes since 20130529: The following defconfigs fail without anything useful in the log: - at91sam9g20_defconfig - at91sam9261_defconfig - at91sam9260_defconfig A manual run reveals why: Can't find default configuration "arch/arm/

linux-next: Tree for May 30

2013-05-29 Thread Stephen Rothwell
Hi all, Changes since 20130529: The xen-arm tree lost its build failure. The net-next tree lost its build warning. I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-nex