From: Kumar Gala <galak@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: "akpm@osdl.org Morton" <akpm@osdl.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
nkalmala@gmail.com
Subject: Re: [patch 1/3] ppc: booke reg MCSR msg misquoted
Date: Fri, 17 Nov 2006 00:36:34 -0600 [thread overview]
Message-ID: <46E7C133-FEE9-4DBD-A298-BEF957F9C39E@kernel.crashing.org> (raw)
In-Reply-To: <200611090352.kA93quLV003810@shell0.pdx.osdl.net>
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
On Nov 8, 2006, at 9:52 PM, akpm@osdl.org wrote:
> From: nkalmala <nkalmala@gmail.com>
>
> PPC/booke reg MCSR value misquoted
>
> Signed-off-by: nkalmala <nkalmala@gmail.com>
> Cc: Paul Mackerras <paulus@samba.org>
> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Cc: <linuxppc-dev@ozlabs.org>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
> ---
>
> arch/ppc/kernel/traps.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff -puN arch/ppc/kernel/traps.c~ppc-booke-reg-mcsr-msg-misquoted
> arch/ppc/kernel/traps.c
> --- a/arch/ppc/kernel/traps.c~ppc-booke-reg-mcsr-msg-misquoted
> +++ a/arch/ppc/kernel/traps.c
> @@ -316,7 +316,7 @@ void machine_check_exception(struct pt_r
> if (reason & MCSR_BUS_RBERR)
> printk("Bus - Read Data Bus Error\n");
> if (reason & MCSR_BUS_WBERR)
> - printk("Bus - Read Data Bus Error\n");
> + printk("Bus - Write Data Bus Error\n");
> if (reason & MCSR_BUS_IPERR)
> printk("Bus - Instruction Parity Error\n");
> if (reason & MCSR_BUS_RPERR)
> _
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
prev parent reply other threads:[~2006-11-17 6:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 3:52 [patch 1/3] ppc: booke reg MCSR msg misquoted akpm
2006-11-17 6:36 ` Kumar Gala [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=46E7C133-FEE9-4DBD-A298-BEF957F9C39E@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=nkalmala@gmail.com \
--cc=paulus@samba.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