From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Neuling <mikey@neuling.org>
Cc: mikey@neuling.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: powerpc: Teach oops about radix vectors
Date: Thu, 4 May 2017 08:18:53 +1000 (AEST) [thread overview]
Message-ID: <3wJCHL2Sc3z9rxm@ozlabs.org> (raw)
In-Reply-To: <20170316030440.32320-1-mikey@neuling.org>
On Thu, 2017-03-16 at 03:04:40 UTC, Michael Neuling wrote:
> Currently if we oops caused by an 0x380 or 0x480 exception, we get a
> print which assumes SLB problems. With radix, these vectors have
> different meanings.
>
> This patch updates the oops message to reflect these different
> meanings.
>
> Signed-off-by: Michael Neuling <mikey@neuling.org>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/8915bcd68b2547c819b8a2a33c0981
cheers
prev parent reply other threads:[~2017-05-03 22:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 3:04 [PATCH] powerpc: Teach oops about radix vectors Michael Neuling
2017-05-03 22:18 ` Michael Ellerman [this message]
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=3wJCHL2Sc3z9rxm@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.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;
as well as URLs for NNTP newsgroup(s).