Re: linux-next: build warning after merge of the final tree
On Mon, 17 Dec 2012 14:34:15 +1100 Stephen Rothwell s...@canb.auug.org.au wrote: Hi all, On Mon, 17 Dec 2012 14:22:38 +1100 Stephen Rothwell s...@canb.auug.org.au wrote: After merging the final tree, today's linux-next build (powerpc allnoconfig) produced this warning: warning: (PPC) selects SPARSE_IRQ which has unmet direct dependencies (HAVE_GENERIC_HARDIRQS (IRQ_DOMAIN DEBUG_FS || MAY_HAVE_SPARSE_IRQ)) I don't know what introduced that. Actually probably caused by commit a1eaa3bc8247 (Kconfig: fix Irq Subsystem menu) from the akpm tree. kconfig-fix-irq-subsystem-menu.patch was causing various problems so I have dropped it. ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
linux-next: build warning after merge of the final tree
Hi all, After merging the final tree, today's linux-next build (powerpc allnoconfig) produced this warning: warning: (PPC) selects SPARSE_IRQ which has unmet direct dependencies (HAVE_GENERIC_HARDIRQS (IRQ_DOMAIN DEBUG_FS || MAY_HAVE_SPARSE_IRQ)) I don't know what introduced that. -- Cheers, Stephen Rothwells...@canb.auug.org.au pgpxcpVMyfcPF.pgp Description: PGP signature ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: linux-next: build warning after merge of the final tree
Hi all, On Mon, 17 Dec 2012 14:22:38 +1100 Stephen Rothwell s...@canb.auug.org.au wrote: After merging the final tree, today's linux-next build (powerpc allnoconfig) produced this warning: warning: (PPC) selects SPARSE_IRQ which has unmet direct dependencies (HAVE_GENERIC_HARDIRQS (IRQ_DOMAIN DEBUG_FS || MAY_HAVE_SPARSE_IRQ)) I don't know what introduced that. Actually probably caused by commit a1eaa3bc8247 (Kconfig: fix Irq Subsystem menu) from the akpm tree. -- Cheers, Stephen Rothwells...@canb.auug.org.au pgpAfjrTYrnYx.pgp Description: PGP signature ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
linux-next: build warning after merge of the final tree (tip/powerpc tree related)
Hi all, After merging the final tree, today's linux-next build (powerpc allnoconfig) produced these warnings: kernel/time/clocksource.c: In function '__clocksource_updatefreq_scale': kernel/time/clocksource.c:655: warning: comparison of distinct pointer types lacks a cast kernel/time/clocksource.c:655: warning: right shift count = width of type kernel/time/clocksource.c:655: warning: passing argument 1 of '__div64_32' from incompatible pointer type include/asm-generic/div64.h:35: note: expected 'uint64_t *' but argument is of type 'long unsigned int *' kernel/time/clocksource.c:656: warning: comparison of distinct pointer types lacks a cast kernel/time/clocksource.c:656: warning: right shift count = width of type kernel/time/clocksource.c:656: warning: passing argument 1 of '__div64_32' from incompatible pointer type include/asm-generic/div64.h:35: note: expected 'uint64_t *' but argument is of type 'long unsigned int *' kernel/time/clockevents.c: In function 'clockevents_config': kernel/time/clockevents.c:211: warning: comparison of distinct pointer types lacks a cast kernel/time/clockevents.c:211: warning: right shift count = width of type kernel/time/clockevents.c:211: warning: passing argument 1 of '__div64_32' from incompatible pointer type include/asm-generic/div64.h:35: note: expected 'uint64_t *' but argument is of type 'long unsigned int *' This is a 32 bit build. -- Cheers, Stephen Rothwells...@canb.auug.org.au http://www.canb.auug.org.au/~sfr/ pgpCLlsbxLfIB.pgp Description: PGP signature ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
linux-next: build warning after merge of the final tree (powercp tree related)
Hi all, After merging the final tree, today's linux-next build (powerpc64 allnoconfig) produced this warning: WARNING: vmlinux.o(.text+0x907a): Section mismatch in reference from the variable generic_secondary_common_init to the variable .init.data:boot_cpu_count The function generic_secondary_common_init() references the variable __initdata boot_cpu_count. This is often because generic_secondary_common_init lacks a __initdata annotation or the annotation of boot_cpu_count is wrong. Caused by commit 9d07bc841c97 (powerpc: Properly handshake CPUs going out of boot spin loop). -- Cheers, Stephen Rothwells...@canb.auug.org.au http://www.canb.auug.org.au/~sfr/ pgpXRgjS8YIKo.pgp Description: PGP signature ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
