LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Olof Johansson <olof@lixom.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: Don't use generic machine check parsing everywhere
Date: Tue, 11 Sep 2007 06:58:12 +1000	[thread overview]
Message-ID: <18149.45028.597999.740370@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20070905024159.GB27139@lixom.net>

Olof Johansson writes:

> If a platform provide it's own machine check handler, assume that code
> will handle the reason parsing and reporting the error. The current
> default fall-though only makes sense on a few 32-bit platforms that
> lack individual handlers.

Might be nice to put that code into a function of its own, called
print_6xx_machine_check or something similar.

Paul.

  reply	other threads:[~2007-09-10 20:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-05  2:41 [PATCH] powerpc: Don't use generic machine check parsing everywhere Olof Johansson
2007-09-10 20:58 ` Paul Mackerras [this message]
2007-09-20 19:11   ` [PATCH] powerpc: Separate out legacy MCE parsers Olof Johansson

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=18149.45028.597999.740370@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=olof@lixom.net \
    /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