From: Alexander Graf <agraf@suse.de>
To: Anton Blanchard <anton@samba.org>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] target-ppc: Fix invalid SPR read/write warnings
Date: Thu, 2 May 2013 00:59:14 +0200 [thread overview]
Message-ID: <0257FDE1-2E6C-4B60-A59C-811704CB6383@suse.de> (raw)
In-Reply-To: <20130501204359.58d02661@kryten>
On 01.05.2013, at 12:43, Anton Blanchard wrote:
>
> Invalid and privileged SPR warnings currently print the wrong
> address. While fixing that, also make it clear that we are
> printing both the decimal and hexadecimal SPR number.
>
> Before:
>
> Trying to read invalid spr 896 380 at 0000000000000714
>
> After:
>
> Trying to read invalid spr 896 (0x380) at 0000000000000710
>
> Signed-off-by: Anton Blanchard <anton@au1.ibm.com>
Thanks, applied both to ppc-next. Welcome to the wonderful world of QEMU ;).
Alex
prev parent reply other threads:[~2013-05-01 22:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 10:43 [Qemu-devel] [PATCH 1/2] target-ppc: Fix invalid SPR read/write warnings Anton Blanchard
2013-05-01 10:44 ` [Qemu-devel] [PATCH 2/2] target-ppc: Add read and write of PPR SPR Anton Blanchard
2013-05-01 22:59 ` Alexander Graf [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=0257FDE1-2E6C-4B60-A59C-811704CB6383@suse.de \
--to=agraf@suse.de \
--cc=anton@samba.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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).