From: Randy Dunlap <rdunlap@xenotime.net>
To: Jiaju Zhang <jjzhang@suse.de>
Cc: linux-kbuild@vger.kernel.org, jkosina@suse.cz, mmarek@suse.cz
Subject: Re: [PATCH] Kconfig: Fix help message for DEFAULT_HUNG_TASK_TIMEOUT
Date: Thu, 08 Sep 2011 14:08:32 -0700 [thread overview]
Message-ID: <4E692ED0.5040906@xenotime.net> (raw)
In-Reply-To: <1314783809-20903-1-git-send-email-jjzhang@suse.de>
On 08/31/11 02:43, Jiaju Zhang wrote:
> Added missing _secs in the help message of config DEFAULT_HUNG_TASK_TIMEOUT.
>
> Signed-off-by: Jiaju Zhang <jjzhang@suse.de>
> ---
> lib/Kconfig.debug | 5 +++--
> 1 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index c0cb9c4..f285553 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -248,8 +248,9 @@ config DEFAULT_HUNG_TASK_TIMEOUT
> to determine when a task has become non-responsive and should
> be considered hung.
>
> - It can be adjusted at runtime via the kernel.hung_task_timeout
> - sysctl or by writing a value to /proc/sys/kernel/hung_task_timeout.
> + It can be adjusted at runtime via the kernel.hung_task_timeout_secs
> + sysctl or by writing a value to
> + /proc/sys/kernel/hung_task_timeout_secs.
>
> A timeout of 0 disables the check. The default is two minutes.
> Keeping the default should be fine in most cases.
Acked-by: Randy Dunlap <rdunlap@xenotime.net>
Jiri, merge in trivial tree?
Jiaju, would you also add 'hung_task_timeout_secs' to
Documentation/sysctl/kernel.txt, please?
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-09-08 22:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 9:43 [PATCH] Kconfig: Fix help message for DEFAULT_HUNG_TASK_TIMEOUT Jiaju Zhang
2011-09-08 21:08 ` Randy Dunlap [this message]
2011-09-09 7:46 ` Jiaju Zhang
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=4E692ED0.5040906@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=jjzhang@suse.de \
--cc=jkosina@suse.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.cz \
/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