summaryrefslogtreecommitdiff
path: root/arch
diff options
context:
space:
mode:
authorRussell King <rmk@dyn-67.arm.linux.org.uk>2007-07-05 22:59:51 +0400
committerRussell King <rmk+kernel@arm.linux.org.uk>2007-07-05 22:59:51 +0400
commit082f47a79bfc8a526b9a3e14a0ae9504fc09cc12 (patch)
treeb51f42f5694afd4719bfe727d0ab1707c77dd83f /arch
parent7b9c7b4d07fd8981193a2c4ecb650566f42d1219 (diff)
downloadlinux-082f47a79bfc8a526b9a3e14a0ae9504fc09cc12.tar.xz
[ARM] always allow dump_stack() to produce a backtrace
Don't make this dependent on CONFIG_DEBUG_KERNEL - if we hit a WARN_ON we need the stack trace to work out how we got to that point. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Diffstat (limited to 'arch')
-rw-r--r--arch/arm/kernel/traps.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/arch/arm/kernel/traps.c b/arch/arm/kernel/traps.c
index 1b68d365d0e1..237f4999b9a1 100644
--- a/arch/arm/kernel/traps.c
+++ b/arch/arm/kernel/traps.c
@@ -181,9 +181,7 @@ static void dump_backtrace(struct pt_regs *regs, struct task_struct *tsk)
void dump_stack(void)
{
-#ifdef CONFIG_DEBUG_ERRORS
__backtrace();
-#endif
}
EXPORT_SYMBOL(dump_stack);