From: Randy Dunlap <randy.dunlap@xxxxxxxxxx> DRBD_TRACE should depend on TRACING. It's also possible that TRACEPOINTS should depend on TRACING. arch/x86/built-in.o: In function `default_idle': (.text+0x145a1): undefined reference to `__tracepoint_power_start' arch/x86/built-in.o: In function `default_idle': (.text+0x145d4): undefined reference to `__tracepoint_power_start' arch/x86/built-in.o: In function `mwait_idle_with_hints': (.text+0x1583d): undefined reference to `__tracepoint_power_start' arch/x86/built-in.o: In function `mwait_idle_with_hints': (.text+0x15870): undefined reference to `__tracepoint_power_start' arch/x86/built-in.o: In function `mwait_idle': process.c:(.text+0x15b92): undefined reference to `__tracepoint_power_start' arch/x86/built-in.o:process.c:(.text+0x15bbe): more undefined references to `__tracepoint_power_start' follow arch/x86/built-in.o: In function `poll_idle': process.c:(.text+0x160bd): undefined reference to `__tracepoint_power_end' process.c:(.text+0x160e9): undefined reference to `__tracepoint_power_end' drivers/built-in.o: In function `cpuidle_idle_call': cpuidle.c:(.text+0x517f16): undefined reference to `__tracepoint_power_end' cpuidle.c:(.text+0x517f49): undefined reference to `__tracepoint_power_end' Signed-off-by: Randy Dunlap <randy.dunlap@xxxxxxxxxx> --- drivers/block/drbd/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- linux-next-20090925.orig/drivers/block/drbd/Kconfig +++ linux-next-20090925/drivers/block/drbd/Kconfig @@ -40,7 +40,7 @@ config BLK_DEV_DRBD config DRBD_TRACE tristate "DRBD tracing" - depends on BLK_DEV_DRBD + depends on BLK_DEV_DRBD && TRACING select TRACEPOINTS default n help -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
