From: li guang <lig.fnst@cn.fujitsu.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/3] debugcon: fix compiler warning when open DEBUG_DEBUGCON
Date: Mon, 15 Apr 2013 08:25:58 +0800 [thread overview]
Message-ID: <1365985558.20662.0.camel@liguang.fnst.cn.fujitsu.com> (raw)
In-Reply-To: <5167FBDB.1080402@suse.de>
在 2013-04-12五的 14:19 +0200,Andreas Färber写道:
> Am 12.04.2013 06:12, schrieb liguang:
> > compiler warnings:
> > CC hw/char/debugcon.o
> > hw/char/debugcon.c: In function ‘debugcon_ioport_write’:
> > hw/char/debugcon.c:58: warning: format ‘%02x’ expects type ‘unsigned int’, but argument 3 has type ‘uint64_t’
> > hw/char/debugcon.c: In function ‘debugcon_ioport_read’:
> > hw/char/debugcon.c:70: warning: format ‘%04x’ expects type ‘unsigned int’, but argument 2 has type ‘hwaddr’
> >
> > Signed-off-by: liguang <lig.fnst@cn.fujitsu.com>
> > ---
> > hw/char/debugcon.c | 4 ++--
> > 1 files changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/hw/char/debugcon.c b/hw/char/debugcon.c
> > index b52cbeb..4cf07c6 100644
> > --- a/hw/char/debugcon.c
> > +++ b/hw/char/debugcon.c
> > @@ -55,7 +55,7 @@ static void debugcon_ioport_write(void *opaque, hwaddr addr, uint64_t val,
> > unsigned char ch = val;
> >
> > #ifdef DEBUG_DEBUGCON
> > - printf(" [debugcon: write addr=0x%04llx val=0x%02x]\n", addr, val);
> > + printf(" [debugcon: write addr=0x%04llx val=0x%02llx]\n", addr, val);
> > #endif
> >
> > qemu_chr_fe_write(s->chr, &ch, 1);
> > @@ -67,7 +67,7 @@ static uint64_t debugcon_ioport_read(void *opaque, hwaddr addr, unsigned width)
> > DebugconState *s = opaque;
> >
> > #ifdef DEBUG_DEBUGCON
> > - printf("debugcon: read addr=0x%04x\n", addr);
> > + printf("debugcon: read addr=0x%04llx\n", addr);
> > #endif
> >
> > return s->readback;
>
> Please see PRIx comment on 1/3.
>
right, thanks!
next prev parent reply other threads:[~2013-04-15 0:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 4:12 [Qemu-devel] [PATCH 1/3] debugcon: fix always print "addr=0x0, val=0x0" bug liguang
2013-04-12 4:12 ` [Qemu-devel] [PATCH 2/3] debugcon: make debug message more readable liguang
2013-04-12 4:12 ` [Qemu-devel] [PATCH 3/3] debugcon: fix compiler warning when open DEBUG_DEBUGCON liguang
2013-04-12 12:19 ` Andreas Färber
2013-04-15 0:25 ` li guang [this message]
2013-04-12 12:16 ` [Qemu-devel] [PATCH 1/3] debugcon: fix always print "addr=0x0, val=0x0" bug Andreas Färber
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=1365985558.20662.0.camel@liguang.fnst.cn.fujitsu.com \
--to=lig.fnst@cn.fujitsu.com \
--cc=afaerber@suse.de \
--cc=qemu-devel@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).