From: Daniel Thompson <daniel.thompson@linaro.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Kiran Raparthy <kiran.kumar@linaro.org>,
linux-kernel@vger.kernel.org, Colin Cross <ccross@android.com>,
Jason Wessel <jason.wessel@windriver.com>,
kgdb-bugreport@lists.sourceforge.net,
Android Kernel Team <kernel-team@android.com>,
John Stultz <john.stultz@linaro.org>,
Sumit Semwal <sumit.semwal@linaro.org>
Subject: Re: [RFC v4] debug: prevent entering debug mode on panic/exception.
Date: Wed, 07 Jan 2015 08:57:30 +0000 [thread overview]
Message-ID: <54ACF4FA.2080309@linaro.org> (raw)
In-Reply-To: <20150106131608.a756b9e8aaf8c496099a5736@linux-foundation.org>
On 06/01/15 21:16, Andrew Morton wrote:
> On Tue, 06 Jan 2015 15:31:31 +0000 Daniel Thompson <daniel.thompson@linaro.org> wrote:
>
>> On 06/01/15 00:14, Andrew Morton wrote:
>>> We appear to have forgotten to document panic_timeout. Sigh.
>>
>> I knew I'd seen it somewhere...
>>
>> Once its been sysctlised it ends up called "panic":
>> https://www.kernel.org/doc/Documentation/sysctl/kernel.txt
>
> Confused. That file doesn't mention panic_timeout. But it is the
> place where panic_timeout can be described.
The sysctl is called "panic" (as is the closely related kernel parameter)
The name panic_timeout is used only for the C symbol presumably because
panic was already used for something else...
Daniel.
prev parent reply other threads:[~2015-01-07 8:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 12:38 [RFC v4] debug: prevent entering debug mode on panic/exception Kiran Raparthy
2015-01-06 0:14 ` Andrew Morton
2015-01-06 5:01 ` Kiran Raparthy
2015-01-06 15:25 ` Daniel Thompson
2015-01-06 21:17 ` Andrew Morton
2015-01-07 3:36 ` Kiran Raparthy
2015-01-06 15:31 ` Daniel Thompson
2015-01-06 21:16 ` Andrew Morton
2015-01-07 8:57 ` Daniel Thompson [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=54ACF4FA.2080309@linaro.org \
--to=daniel.thompson@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=ccross@android.com \
--cc=jason.wessel@windriver.com \
--cc=john.stultz@linaro.org \
--cc=kernel-team@android.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=kiran.kumar@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sumit.semwal@linaro.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;
as well as URLs for NNTP newsgroup(s).