qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	Antony Pavlov <antonynpavlov@gmail.com>,
	Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Subject: [Qemu-devel] [PATCH 2/7] gt64xxx.c: fix length modifier in DPRINTF format string
Date: Wed,  5 Oct 2011 09:47:54 +0100	[thread overview]
Message-ID: <1317804479-5876-3-git-send-email-stefanha@linux.vnet.ibm.com> (raw)
In-Reply-To: <1317804479-5876-1-git-send-email-stefanha@linux.vnet.ibm.com>

From: Antony Pavlov <antonynpavlov@gmail.com>

The commit fc2bf44972349b078d8310466c3866615500e67f
changed the type of val argument of the function gt64120_writel()
from uint32_t to uint64_t, so we need to change the corresponding
length modifier from "%x" to "%" PRIx64.

Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com>
Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
---
 hw/gt64xxx.c |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/hw/gt64xxx.c b/hw/gt64xxx.c
index 1c34253..73454ff 100644
--- a/hw/gt64xxx.c
+++ b/hw/gt64xxx.c
@@ -543,19 +543,19 @@ static void gt64120_writel (void *opaque, target_phys_addr_t addr,
         /* not really implemented */
         s->regs[saddr] = ~(~(s->regs[saddr]) | ~(val & 0xfffffffe));
         s->regs[saddr] |= !!(s->regs[saddr] & 0xfffffffe);
-        DPRINTF("INTRCAUSE %x\n", val);
+        DPRINTF("INTRCAUSE %" PRIx64 "\n", val);
         break;
     case GT_INTRMASK:
         s->regs[saddr] = val & 0x3c3ffffe;
-        DPRINTF("INTRMASK %x\n", val);
+        DPRINTF("INTRMASK %" PRIx64 "\n", val);
         break;
     case GT_PCI0_ICMASK:
         s->regs[saddr] = val & 0x03fffffe;
-        DPRINTF("ICMASK %x\n", val);
+        DPRINTF("ICMASK %" PRIx64 "\n", val);
         break;
     case GT_PCI0_SERR0MASK:
         s->regs[saddr] = val & 0x0000003f;
-        DPRINTF("SERR0MASK %x\n", val);
+        DPRINTF("SERR0MASK %" PRIx64 "\n", val);
         break;
 
     /* Reserved when only PCI_0 is configured. */
-- 
1.7.6.3

  parent reply	other threads:[~2011-10-05  8:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-05  8:47 [Qemu-devel] [PULL 0/7] Trivial patches for September 22 to October 5 2011 Stefan Hajnoczi
2011-10-05  8:47 ` [Qemu-devel] [PATCH 1/7] makefile: extract tools-obj-y Stefan Hajnoczi
2011-10-05  8:47 ` Stefan Hajnoczi [this message]
2011-10-05  8:47 ` [Qemu-devel] [PATCH 3/7] gt64xxx.c: remove reference to non-existing ISD_handle field Stefan Hajnoczi
2011-10-05  8:47 ` [Qemu-devel] [PATCH 4/7] lsi: Fix tag reference in debug print Stefan Hajnoczi
2011-10-05  8:47 ` [Qemu-devel] [PATCH 5/7] target-arm: Fix typo Stefan Hajnoczi
2011-10-05  8:47 ` [Qemu-devel] [PATCH 6/7] Fix mismatching allocation and deallocation Stefan Hajnoczi
2011-10-05  8:47 ` [Qemu-devel] [PATCH 7/7] linux-user: Remove unused code Stefan Hajnoczi
2011-10-10 14:44 ` [Qemu-devel] [PULL 0/7] Trivial patches for September 22 to October 5 2011 Anthony Liguori

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=1317804479-5876-3-git-send-email-stefanha@linux.vnet.ibm.com \
    --to=stefanha@linux.vnet.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=antonynpavlov@gmail.com \
    --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).