qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org,
	stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [RESEND PATCH] ioapic: fix build with DEBUG_IOAPIC
Date: Mon, 19 Mar 2012 11:22:18 +0800	[thread overview]
Message-ID: <4F66A66A.20000@redhat.com> (raw)
In-Reply-To: <4F6316D0.6010105@suse.de>

On 03/16/2012 06:32 PM, Andreas Färber wrote:
> Am 16.03.2012 10:10, schrieb Jason Wang:
>> ioapic.c:198: error: format ‘%08x’ expects type ‘unsigned int’, but argument 3 has type ‘uint64_t’
>>
>> Signed-off-by: Jason Wang<jasowang@redhat.com>
> PRIx64 is indeed needed here. However, this drops the 08 without mention
> in the commit message - was it intended?

Not intended, my fault, thanks for pointing this.
> Andreas
>
>> ---
>>   hw/ioapic.c |    2 +-
>>   1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/hw/ioapic.c b/hw/ioapic.c
>> index 3fee011..1ff31a1 100644
>> --- a/hw/ioapic.c
>> +++ b/hw/ioapic.c
>> @@ -195,7 +195,7 @@ ioapic_mem_write(void *opaque, target_phys_addr_t addr, uint64_t val,
>>           if (size != 4) {
>>               break;
>>           }
>> -        DPRINTF("write: %08x = %08x\n", s->ioregsel, val);
>> +        DPRINTF("write: %08x = %" PRIx64 "\n", s->ioregsel, val);
>>           switch (s->ioregsel) {
>>           case IOAPIC_REG_ID:
>>               s->id = (val>>  IOAPIC_ID_SHIFT)&  IOAPIC_ID_MASK;

      reply	other threads:[~2012-03-19  3:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-16  9:10 [Qemu-devel] [RESEND PATCH] ioapic: fix build with DEBUG_IOAPIC Jason Wang
2012-03-16 10:32 ` Andreas Färber
2012-03-19  3:22   ` Jason Wang [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=4F66A66A.20000@redhat.com \
    --to=jasowang@redhat.com \
    --cc=afaerber@suse.de \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.com \
    /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).