From 8ae34ea7e8e655a9afe477062f1d91a3700959b5 Mon Sep 17 00:00:00 2001 From: Harish Jenny K N Date: Wed, 20 Aug 2014 11:56:17 +0530 Subject: [PATCH] lockup-watchdogs: Fix a typo s/BOOTPARAM_HARDLOCKUP_PANIC/BOOTPARAM_SOFTLOCKUP_PANIC Signed-off-by: Harish Jenny K N Acked-by: Randy Dunlap Signed-off-by: Jiri Kosina --- Documentation/lockup-watchdogs.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/lockup-watchdogs.txt b/Documentation/lockup-watchdogs.txt index d2a3660..ab0baa6 100644 --- a/Documentation/lockup-watchdogs.txt +++ b/Documentation/lockup-watchdogs.txt @@ -12,7 +12,7 @@ stack trace is displayed upon detection and, by default, the system will stay locked up. Alternatively, the kernel can be configured to panic; a sysctl, "kernel.softlockup_panic", a kernel parameter, "softlockup_panic" (see "Documentation/kernel-parameters.txt" for -details), and a compile option, "BOOTPARAM_HARDLOCKUP_PANIC", are +details), and a compile option, "BOOTPARAM_SOFTLOCKUP_PANIC", are provided for this. A 'hardlockup' is defined as a bug that causes the CPU to loop in -- 2.7.4