From: Ralf Baechle <ralf@linux-mips.org>
To: Shinya Kuribayashi <skuribay@pobox.com>
Cc: jbaron@akamai.com, mingo@kernel.org, benh@kernel.crashing.org,
paulus@samba.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, linux-mips@linux-mips.org,
florian@openwrt.org, jchandra@broadcom.com,
ganesanr@broadcom.com
Subject: Re: [PATCH v2] panic: Make panic_timeout configurable
Date: Tue, 19 Nov 2013 17:38:12 +0100 [thread overview]
Message-ID: <20131119163811.GD13331@linux-mips.org> (raw)
In-Reply-To: <528B7AEF.7020805@pobox.com>
On Tue, Nov 19, 2013 at 11:51:27PM +0900, Shinya Kuribayashi wrote:
> IIRC we had set it to 180 seconds for some historical reasons, but
> I'm afraid nobody can recall the reason why it's set so in 2013...
> Anyway I was thinking it too long and reduced to a few seconds locally
> when debugging, so there shouldn't be a problem with this change.
I think one motivation was to have boards reboot automatically avoiding
the need to walk over to the board just powercycle or reset it - let
alone reseting by emailing/phoning an admin!
But that's a development-specific motivation and it shouldn't result
in a hardcoded reboot timeout for everybody.
Ralf
next prev parent reply other threads:[~2013-11-19 16:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131118210436.233B5202A@prod-mail-relay06.akamai.com>
2013-11-19 9:02 ` [PATCH v2] panic: Make panic_timeout configurable Ralf Baechle
2013-11-19 14:51 ` Shinya Kuribayashi
2013-11-19 16:38 ` Ralf Baechle [this message]
2013-11-19 17:11 ` Jason Baron
2013-11-19 17:22 ` Ralf Baechle
2013-11-21 8:44 ` Jayachandran C.
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=20131119163811.GD13331@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=florian@openwrt.org \
--cc=ganesanr@broadcom.com \
--cc=jbaron@akamai.com \
--cc=jchandra@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mingo@kernel.org \
--cc=paulus@samba.org \
--cc=skuribay@pobox.com \
/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