From: "Andreas Färber" <afaerber@suse.de>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-trivial <qemu-trivial@nongnu.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] serial: Fix debug format strings
Date: Tue, 19 Mar 2013 14:29:21 +0100 [thread overview]
Message-ID: <51486831.4070802@suse.de> (raw)
In-Reply-To: <1363692343-22299-1-git-send-email-kwolf@redhat.com>
Am 19.03.2013 12:25, schrieb Kevin Wolf:
> This fixes the build of hw/serial.c with DEBUG_SERIAL enabled.
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
> hw/serial.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hw/serial.c b/hw/serial.c
> index 48a5eb6..0ccc499 100644
> --- a/hw/serial.c
> +++ b/hw/serial.c
> @@ -306,7 +306,7 @@ static void serial_ioport_write(void *opaque, hwaddr addr, uint64_t val,
> SerialState *s = opaque;
>
> addr &= 7;
> - DPRINTF("write addr=0x%02x val=0x%02x\n", addr, val);
> + DPRINTF("write addr=0x%" HWADDR_PRIx " val=0x%" PRIx64 "\n", addr, val);
Are you intentionally dropping 02 in both places? That changes output FWIW.
Andreas
> switch(addr) {
> default:
> case 0:
> @@ -527,7 +527,7 @@ static uint64_t serial_ioport_read(void *opaque, hwaddr addr, unsigned size)
> ret = s->scr;
> break;
> }
> - DPRINTF("read addr=0x%02x val=0x%02x\n", addr, ret);
> + DPRINTF("read addr=0x%" HWADDR_PRIx " val=0x%02x\n", addr, ret);
> return ret;
> }
>
>
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-03-19 13:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 11:25 [Qemu-devel] [PATCH] serial: Fix debug format strings Kevin Wolf
2013-03-19 12:51 ` Markus Armbruster
2013-03-19 13:29 ` Andreas Färber [this message]
2013-03-19 13:42 ` Kevin Wolf
2013-03-22 12:31 ` Stefan Hajnoczi
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=51486831.4070802@suse.de \
--to=afaerber@suse.de \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).