aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/lockup-watchdogs.txt
diff options
context:
space:
mode:
authorHarish Jenny K N <harish_kandiga@mentor.com>2014-08-20 06:26:17 (GMT)
committerJiri Kosina <jkosina@suse.cz>2014-08-26 07:35:52 (GMT)
commit8ae34ea7e8e655a9afe477062f1d91a3700959b5 (patch)
tree0f17ceb4a48098d03ba4c73460f9e404ca16b91c /Documentation/lockup-watchdogs.txt
parent924064e93970a1b45d83ac67165f0570f4649e0f (diff)
lockup-watchdogs: Fix a typo
s/BOOTPARAM_HARDLOCKUP_PANIC/BOOTPARAM_SOFTLOCKUP_PANIC Signed-off-by: Harish Jenny K N <harish_kandiga@mentor.com> Acked-by: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'Documentation/lockup-watchdogs.txt')
-rw-r--r--Documentation/lockup-watchdogs.txt2
1 files changed, 1 insertions, 1 deletions
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

Privacy Policy