lkml.org 
[lkml]   [2014]   [Aug]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] lockup-watchdogs: Fix a typo
On 08/19/14 23:26, harish_kandiga@mentor.com wrote:
> From: Harish Jenny K N <harish_kandiga@mentor.com>
>
> 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>

Jiri, please add to the trivial tree.

Thanks.

> ---
> 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
>


--
~Randy


\
 
 \ /
  Last update: 2014-08-20 09:01    [W:0.043 / U:0.080 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site