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:

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. --

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

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

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