All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: Vivek Goyal <vgoyal@redhat.com>,
	Lai Jiangshan <laijs@cn.fujitsu.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Brayan Arraes <brayan@yack.com.br>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"Ken'ichi Ohmichi" <oomichi@mxs.nes.nec.co.jp>
Subject: Re: [PATCH] sysrq, kdump: fix regression, revert "simplify sysrq-c handler"
Date: Thu, 23 Jul 2009 10:10:20 +0900	[thread overview]
Message-ID: <4A67B87C.5030104@jp.fujitsu.com> (raw)
In-Reply-To: <20090722193831.GA4718@hmsreliant.think-freely.org>

Neil Horman wrote:
> On Wed, Jul 22, 2009 at 09:42:11AM -0400, Vivek Goyal wrote:
>> Can't we just set panic_on_oops = 1 in sysrq_handle_crash()? This will
>> make sure that we test oops path as well as have consistent behavior
>> between two methods of sysrc-c invocation.
>>
> Thats a good point too, seems simpler than the other approach.

OK, I'll take this way.  Please wait for a moment for a patch.

Thanks,
H.Seto


  reply	other threads:[~2009-07-23  1:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-20 12:46 [PATCH] sysrq, kdump: fix regression, revert "simplify sysrq-c handler" Lai Jiangshan
2009-07-20 19:22 ` Eric W. Biederman
2009-07-20 21:16   ` Neil Horman
2009-07-21  6:46     ` Lai Jiangshan
2009-07-21 22:18       ` Eric W. Biederman
2009-07-21  6:00   ` Lai Jiangshan
2009-07-21  6:56     ` Eric W. Biederman
2009-07-21  6:49 ` Hidetoshi Seto
2009-07-21 11:08   ` Neil Horman
2009-07-21 12:16     ` Lai Jiangshan
2009-07-22  2:01     ` Hidetoshi Seto
2009-07-22 11:10       ` Neil Horman
2009-07-22 13:42         ` Vivek Goyal
2009-07-22 19:38           ` Neil Horman
2009-07-23  1:10             ` Hidetoshi Seto [this message]
2009-07-23  1:09         ` Hidetoshi Seto

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=4A67B87C.5030104@jp.fujitsu.com \
    --to=seto.hidetoshi@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=brayan@yack.com.br \
    --cc=ebiederm@xmission.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=oomichi@mxs.nes.nec.co.jp \
    --cc=vgoyal@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.