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 Rothwell sfr@canb.auug.org.au
Hi all,
On Mon, 17 Dec 2012 14:22:38 +1100 Stephen Rothwell [off-list ref] 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 Rothwell sfr@canb.auug.org.au
On Mon, 17 Dec 2012 14:34:15 +1100
Stephen Rothwell [off-list ref] wrote:
Hi all,
On Mon, 17 Dec 2012 14:22:38 +1100 Stephen Rothwell [off-list ref] wrote:
quoted
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.