Buildresult: cdrx/powerpc-allmodconfig+ppc64le/powerpc-gcc5 built on Jun 22 2018, 20:40

kisskb

Revisions | Branches | Compilers | Configs | Build Results | Build Failures |

Status:	OK
Date/Time:	Jun 22 2018, 20:40
Duration:	0:12:54.879198
Builder:	ka1
Revision:	mtd: spi-nor: aspeed: limit the maximum SPI frequency (`e30034551410432f84fb90467f6078b0f77775ce)`
Target:	cdrx/powerpc-allmodconfig+ppc64le/powerpc-gcc5
Branch:	cdrx
Compiler:	powerpc-gcc5 (powerpc64le-linux-gcc (GCC) 5.2.0)
Config:	allmodconfig+ppc64le (download)
Log:	Download original Possible warnings (6) <stdin>:1332:2: warning: #warning syscall io_pgetevents not implemented [-Wcpp] arch/powerpc/include/asm/io.h:160:2: warning: 'px_is' may be used uninitialized in this function [-Wmaybe-uninitialized] arch/powerpc/include/asm/io.h:160:2: warning: 'px_cmd' may be used uninitialized in this function [-Wmaybe-uninitialized] WARNING: vmlinux.o(.text+0x36b4): Section mismatch in reference from the variable __boot_from_prom to the function .init.text:prom_init() WARNING: vmlinux.o(.text+0x3944): Section mismatch in reference from the variable start_here_multiplatform to the function .init.text:early_setup() WARNING: vmlinux.o(.text+0x3978): Section mismatch in reference from the variable start_here_common to the function .init.text:start_kernel() Full Log # git rev-parse -q --verify e30034551410432f84fb90467f6078b0f77775ce^{commit} e30034551410432f84fb90467f6078b0f77775ce already have revision, skipping fetch # git checkout -q -f -B kisskb e30034551410432f84fb90467f6078b0f77775ce # git clean -qxdf # < git log -1 # commit e30034551410432f84fb90467f6078b0f77775ce # Author: Cédric Le Goater <clg@kaod.org> # Date: Fri Jun 22 10:09:23 2018 +0200 # # mtd: spi-nor: aspeed: limit the maximum SPI frequency # # The optimize read algo can choose a 100MHz SPI frequency which might # be a bit too high for dual output IO on some chips, for the W25Q256 on # palmetto for instance. The MX66L1G45G on witherspoon should be fine # though. Also, the second chip of the FMC controller does not get any # optimize settings for reads. Only the first is configured by U-Boot. # # To fix these two issues, we introduce a "spi-max-frequency" property # in the device tree which will be used to cap the optimize read # algorithm and we run the algo on the FMC controller chips as well. # # By default, the frequency setting is 50MHz. # # Signed-off-by: Cédric Le Goater <clg@kaod.org> # < /opt/cross/kisskb/gcc-5.2.0-nolibc/powerpc64le-linux/bin/powerpc64le-linux-gcc --version # < git log --format=%s --max-count=1 e30034551410432f84fb90467f6078b0f77775ce # < make -s -j 48 ARCH=powerpc O=/kisskb/build/cdrx_allmodconfig+ppc64le_ppc64le CROSS_COMPILE=/opt/cross/kisskb/gcc-5.2.0-nolibc/powerpc64le-linux/bin/powerpc64le-linux- allmodconfig # Added to kconfig CONFIG_CPU_LITTLE_ENDIAN=y # Added to kconfig CONFIG_BUILD_DOCSRC=n # Added to kconfig CONFIG_MODULE_SIG=n # Added to kconfig CONFIG_SAMPLES=n # yes \n \| make -s -j 48 ARCH=powerpc O=/kisskb/build/cdrx_allmodconfig+ppc64le_ppc64le CROSS_COMPILE=/opt/cross/kisskb/gcc-5.2.0-nolibc/powerpc64le-linux/bin/powerpc64le-linux- oldconfig yes: standard output: Broken pipe yes: write error # make -s -j 48 ARCH=powerpc O=/kisskb/build/cdrx_allmodconfig+ppc64le_ppc64le CROSS_COMPILE=/opt/cross/kisskb/gcc-5.2.0-nolibc/powerpc64le-linux/bin/powerpc64le-linux- /kisskb/src/net/Makefile:24: CC cannot link executables. Skipping bpfilter. <stdin>:1332:2: warning: #warning syscall io_pgetevents not implemented [-Wcpp] /kisskb/src/net/Makefile:24: CC cannot link executables. Skipping bpfilter. In file included from /kisskb/src/include/linux/io.h:25:0, from /kisskb/src/include/linux/of_address.h:7, from /kisskb/src/drivers/ata/ahci_qoriq.c:18: /kisskb/src/drivers/ata/ahci_qoriq.c: In function 'ahci_qoriq_hardreset': /kisskb/src/arch/powerpc/include/asm/io.h:160:2: warning: 'px_is' may be used uninitialized in this function [-Wmaybe-uninitialized] __asm__ __volatile__("sync;"#insn"%U0%X0 %1,%0" \ ^ /kisskb/src/drivers/ata/ahci_qoriq.c:86:14: note: 'px_is' was declared here u32 px_cmd, px_is, px_val; ^ In file included from /kisskb/src/include/linux/io.h:25:0, from /kisskb/src/include/linux/of_address.h:7, from /kisskb/src/drivers/ata/ahci_qoriq.c:18: /kisskb/src/arch/powerpc/include/asm/io.h:160:2: warning: 'px_cmd' may be used uninitialized in this function [-Wmaybe-uninitialized] __asm__ __volatile__("sync;"#insn"%U0%X0 %1,%0" \ ^ /kisskb/src/drivers/ata/ahci_qoriq.c:86:6: note: 'px_cmd' was declared here u32 px_cmd, px_is, px_val; ^ WARNING: vmlinux.o(.text+0x36b4): Section mismatch in reference from the variable __boot_from_prom to the function .init.text:prom_init() The function __boot_from_prom() references the function __init prom_init(). This is often because __boot_from_prom lacks a __init annotation or the annotation of prom_init is wrong. WARNING: vmlinux.o(.text+0x3944): Section mismatch in reference from the variable start_here_multiplatform to the function .init.text:early_setup() The function start_here_multiplatform() references the function __init early_setup(). This is often because start_here_multiplatform lacks a __init annotation or the annotation of early_setup is wrong. WARNING: vmlinux.o(.text+0x3978): Section mismatch in reference from the variable start_here_common to the function .init.text:start_kernel() The function start_here_common() references the function __init start_kernel(). This is often because start_here_common lacks a __init annotation or the annotation of start_kernel is wrong. Completed OK # rm -rf /kisskb/build/cdrx_allmodconfig+ppc64le_ppc64le # Build took: 0:12:54.879198

© Michael Ellerman 2006-2018.