On 08/19/14 23:26, harish_kand...@mentor.com wrote: > From: Harish Jenny K N <harish_kand...@mentor.com> > > s/BOOTPARAM_HARDLOCKUP_PANIC/BOOTPARAM_SOFTLOCKUP_PANIC > > Signed-off-by: Harish Jenny K N <harish_kand...@mentor.com>
Acked-by: Randy Dunlap <rdun...@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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
