From: Randy Dunlap <rdunlap@infradead.org>
To: harish_kandiga@mentor.com
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Jiri Kosina <trivial@kernel.org>
Subject: Re: [PATCH] lockup-watchdogs: Fix a typo
Date: Tue, 19 Aug 2014 23:30:48 -0700 [thread overview]
Message-ID: <53F44098.2050209@infradead.org> (raw)
In-Reply-To: <1408515977-13263-1-git-send-email-harish_kandiga@mentor.com>
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
prev parent reply other threads:[~2014-08-20 6:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 6:26 [PATCH] lockup-watchdogs: Fix a typo harish_kandiga
2014-08-20 6:30 ` Randy Dunlap [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53F44098.2050209@infradead.org \
--to=rdunlap@infradead.org \
--cc=harish_kandiga@mentor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox