From: Andrew Morton <akpm@osdl.org>
To: strosake@austin.ibm.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arch-specific callout in panic()
Date: Sun, 22 Feb 2004 21:34:38 -0800 [thread overview]
Message-ID: <20040222213438.7682ff7b.akpm@osdl.org> (raw)
In-Reply-To: <40398BFE.1040300@austin.ibm.com>
Mike Strosaker <strosake@austin.ibm.com> wrote:
>
> There are some ppc64-specific actions that should be taken upon a
> kernel panic. Rather than adding a new #ifdef in panic(), it seems to
> me that it would be worthwhile to add a single callout, and move the
> arch-specific code out to the arch subtrees. Does this seem reasonable,
> or should another #ifdef be added in panic() to perform the ppc64-
> specific actions?
We have the panic_notifier_list in there. Cannot you hook into that?
next prev parent reply other threads:[~2004-02-23 5:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 5:13 [PATCH] arch-specific callout in panic() Mike Strosaker
2004-02-23 5:34 ` Andrew Morton [this message]
2004-02-23 18:33 ` Mike Strosaker
2004-02-24 4:25 ` Keith Owens
2004-02-23 5:54 ` viro
-- strict thread matches above, loose matches on Subject: below --
2004-02-23 9:25 Arnd Bergmann
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=20040222213438.7682ff7b.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=strosake@austin.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