public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: hidave.darkstar@gmail.com, linux-kernel@vger.kernel.org,
	torvalds@linux-foundation.org
Subject: Re: [PATCH v3] printk: add halt_delay parameter for printk delay in halt phase
Date: Mon, 8 Jun 2009 15:07:43 -0700	[thread overview]
Message-ID: <20090608150743.f2a0e09f.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090608220253.GD22049@elte.hu>

On Tue, 9 Jun 2009 00:02:53 +0200
Ingo Molnar <mingo@elte.hu> wrote:

> The /proc thing definitely makes sense - the boot option was just 
> symmetry to the existing boot-delay approach.

ok.  btw, if we do decide to go with a general printk_delay then we'll
need a touch_nmi_watchdog() in there to keep the NMI watchdog and
softlockup detector away.


  reply	other threads:[~2009-06-08 22:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-08  7:40 [PATCH v3] printk: add halt_delay parameter for printk delay in halt phase Dave Young
2009-06-08  8:12 ` [tip:core/printk] printk: Add halt_delay=<msecs> " tip-bot for Dave Young
2009-06-08  8:14 ` [PATCH v3] printk: add halt_delay " Ingo Molnar
2009-06-08  8:28   ` Andrew Morton
2009-06-08  8:42     ` Dave Young
2009-06-08  8:48       ` Ingo Molnar
2009-06-08 16:26         ` Andrew Morton
2009-06-08 17:15           ` Ingo Molnar
2009-06-08 21:39             ` Andrew Morton
2009-06-08 22:02               ` Ingo Molnar
2009-06-08 22:07                 ` Andrew Morton [this message]
2009-06-08 22:12               ` Ingo Molnar
2009-06-09  1:01               ` Dave Young
2009-06-09  1:35                 ` Dave Young
2009-06-09  2:33                 ` Andrew Morton
2009-06-09  0:48             ` Dave Young
2009-06-08  8:37   ` Dave Young
2009-06-08  8:46     ` Ingo Molnar
2009-06-08  8:56       ` Dave Young
2009-06-08  8:58         ` Ingo Molnar
2009-06-08  9:00           ` Dave Young

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=20090608150743.f2a0e09f.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=hidave.darkstar@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@linux-foundation.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