public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takenori Nagano <t-nagano@ah.jp.nec.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org, vgoyal@in.ibm.com,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	k-miyoshi@cb.jp.nec.com, kexec@lists.infradead.org,
	Bernhard Walle <bwalle@suse.de>, Keith Owens <kaos@ocs.com.au>,
	Andrew Morton <akpm@linux-foundation.org>,
	kdb@oss.sgi.com
Subject: Re: [PATCH 2/2] implement new notifier function to panic_notifier_list
Date: Fri, 05 Oct 2007 13:59:43 +0900	[thread overview]
Message-ID: <4705C4BF.6060308@ah.jp.nec.com> (raw)
In-Reply-To: <20071004090711.456b6338.randy.dunlap@oracle.com>

Randy Dunlap wrote:
> On Thu, 04 Oct 2007 20:38:50 +0900 Takenori Nagano wrote:
> 
>> This patch implements new notifier function to panic_notifier_list. We can
>> change the list of order by debugfs.
>>
>> Thanks,
>>
>> ---
>>
>> Signed-off-by: Takenori Nagano <t-nagano@ah.jp.nec.com>
>>
>> ---
>>   * Returns seconds, approximately.  We don't need nanosecond
>>   * resolution, and we don't need to waste time with a big divide when
>> @@ -193,5 +201,6 @@ __init void spawn_softlockup_task(void)
>>  	cpu_callback(&cpu_nfb, CPU_ONLINE, cpu);
>>  	register_cpu_notifier(&cpu_nfb);
>>
>> -	atomic_notifier_chain_register(&panic_notifier_list, &panic_block);
>> +	tunable_notifier_chain_register(&panic_notifier_list, &panic_block,
>> +						"softlookup", NULL);
>>  }
> 
>                                                 "softlockup"

Hi Randy,

Thank you for reviewing. :)
I'll fix next version.

  reply	other threads:[~2007-10-05  5:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-04 11:38 [PATCH 2/2] implement new notifier function to panic_notifier_list Takenori Nagano
2007-10-04 16:07 ` Randy Dunlap
2007-10-05  4:59   ` Takenori Nagano [this message]
2007-10-05  5:49 ` Vivek Goyal
2007-10-05  6:19   ` Takenori Nagano

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=4705C4BF.6060308@ah.jp.nec.com \
    --to=t-nagano@ah.jp.nec.com \
    --cc=akpm@linux-foundation.org \
    --cc=bwalle@suse.de \
    --cc=ebiederm@xmission.com \
    --cc=k-miyoshi@cb.jp.nec.com \
    --cc=kaos@ocs.com.au \
    --cc=kdb@oss.sgi.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=vgoyal@in.ibm.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