* Alexey Dobriyan <adobriyan@xxxxxxxxx> wrote: > Please, fold this into 32c0bd9624115041cfec31c0436995418083090a > "blktrace: the ftrace interface needs CONFIG_TRACING" > to fix link error on alpha (which doesn't implenent stacktrace support) > > --- a/block/Kconfig > +++ b/block/Kconfig > @@ -51,7 +51,7 @@ config BLK_DEV_IO_TRACE > select DEBUG_FS > select TRACEPOINTS > select TRACING > - select STACKTRACE > + select STACKTRACE if STACKTRACE_SUPPORT > help > Say Y here if you want to be able to trace the block layer actions > on a given queue. Tracing allows you to see any traffic happening This didnt apply to the latest tracing tree due to other, interacting changes - i have applied the commit below - thanks Alexey! Ingo -----------------> >From 510223da040cb7a7d6f524b12eeed03b3845aea1 Mon Sep 17 00:00:00 2001 From: Alexey Dobriyan <adobriyan@xxxxxxxxx> Date: Tue, 10 Feb 2009 00:38:36 +0300 Subject: [PATCH] alpha: fix link error re stacktrace Fix link error on alpha (which doesn't implenent stacktrace support). Signed-off-by: Ingo Molnar <mingo@xxxxxxx> --- kernel/trace/Kconfig | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig index 3a33128..79be773 100644 --- a/kernel/trace/Kconfig +++ b/kernel/trace/Kconfig @@ -310,7 +310,7 @@ config BLK_DEV_IO_TRACE select DEBUG_FS select TRACEPOINTS select TRACING - select STACKTRACE + select STACKTRACE if STACKTRACE_SUPPORT help Say Y here if you want to be able to trace the block layer actions on a given queue. Tracing allows you to see any traffic happening -- 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
