From: Ralf Baechle <ralf@linux-mips.org>
To: Jason Baron <jbaron@akamai.com>
Cc: "mingo@kernel.org" <mingo@kernel.org>,
"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
"paulus@samba.org" <paulus@samba.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
Florian Fainelli <florian@openwrt.org>,
Shinya Kuribayashi <skuribay@ruby.dti.ne.jp>,
Jayachandran C <jchandra@broadcom.com>,
Ganesan Ramalingam <ganesanr@broadcom.com>
Subject: Re: [PATCH v2] panic: Make panic_timeout configurable
Date: Tue, 19 Nov 2013 18:22:06 +0100 [thread overview]
Message-ID: <20131119172205.GE10382@linux-mips.org> (raw)
In-Reply-To: <528B9BC1.7090402@akamai.com>
On Tue, Nov 19, 2013 at 12:11:29PM -0500, Jason Baron wrote:
> > I propose to kill these overrides for sanity unless somebody comes up
> > with a good argument. Patch below.
> >
>
> And so have the mips default be 0? IE drop the arch/mips/Kconfig bits from
> the patch I posted? (Which could of course be configured to a non-zero value
> by the user, if desired.)
Yes.
Ralf
next prev parent reply other threads:[~2013-11-19 17:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 21:04 [PATCH v2] panic: Make panic_timeout configurable Jason Baron
2013-11-18 22:30 ` Andrew Morton
2013-11-18 23:13 ` Jason Baron
2013-11-19 7:09 ` Ingo Molnar
2013-11-19 22:04 ` Jason Baron
2013-11-21 11:16 ` Michael Ellerman
2013-11-21 21:21 ` Jason Baron
2013-11-22 1:54 ` Michael Ellerman
2013-11-19 7:15 ` Ingo Molnar
2013-11-27 6:13 ` Felipe Contreras
2013-11-19 9:02 ` Ralf Baechle
2013-11-19 14:51 ` Shinya Kuribayashi
2013-11-19 16:38 ` Ralf Baechle
2013-11-19 17:11 ` Jason Baron
2013-11-19 17:22 ` Ralf Baechle [this message]
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=20131119172205.GE10382@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@ruby.dti.ne.jp \
/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).