From: Alon Levy <alevy@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Stefan Weil <sw@weilnetz.de>,
Anthony Liguori <aliguori@us.ibm.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 5/5] trace-events: Fix broken build caused by wrong format specifier
Date: Mon, 26 Mar 2012 14:48:16 +0200 [thread overview]
Message-ID: <20120326124816.GB32389@garlic> (raw)
In-Reply-To: <4F7063F3.4070906@suse.de>
On Mon, Mar 26, 2012 at 02:41:23PM +0200, Andreas Färber wrote:
> Am 26.03.2012 14:07, schrieb Stefan Hajnoczi:
> > From: Stefan Weil <sw@weilnetz.de>
> >
> > mem is an uint64_t value, so %lx was wrong.
> >
> > Signed-off-by: Stefan Weil <sw@weilnetz.de>
>
> Alon, you replied with an "ACK". Should an Acked-by be inserted here?
Yes, should have been verbose, sorry. But I don't think it matters much
for this kind of small patch.
>
> Andreas
>
> > Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
> > ---
> > trace-events | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/trace-events b/trace-events
> > index 70f059d..db2cd39 100644
> > --- a/trace-events
> > +++ b/trace-events
> > @@ -726,7 +726,7 @@ ppm_save(const char *filename, void *display_surface) "%s surface=%p"
> > # hw/qxl.c
> > disable qxl_interface_set_mm_time(int qid, uint32_t mm_time) "%d %d"
> > disable qxl_io_write_vga(int qid, const char *mode, uint32_t addr, uint32_t val) "%d %s addr=%u val=%u"
> > -qxl_create_guest_primary(int qid, uint32_t width, uint32_t height, uint64_t mem, uint32_t format, uint32_t position) "%d %dx%d mem=%lx %d,%d"
> > +qxl_create_guest_primary(int qid, uint32_t width, uint32_t height, uint64_t mem, uint32_t format, uint32_t position) "%d %ux%u mem=%" PRIx64 " %u,%u"
> > qxl_create_guest_primary_rest(int qid, int32_t stride, uint32_t type, uint32_t flags) "%d %d,%d,%d"
> > qxl_destroy_primary(int qid) "%d"
> > qxl_enter_vga_mode(int qid) "%d"
>
> --
> 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:[~2012-03-26 12:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 12:07 [Qemu-devel] [PULL 0/5] Trivial patches for 20 to 26 March 2012 Stefan Hajnoczi
2012-03-26 12:07 ` [Qemu-devel] [PATCH 1/5] vl.c: fix '-cpu ?' segfault Stefan Hajnoczi
2012-03-26 12:07 ` [Qemu-devel] [PATCH 2/5] test: remove qemu-ga reference Stefan Hajnoczi
2012-03-26 12:07 ` [Qemu-devel] [PATCH 3/5] qapi: remove print statements from test-qmp-commands Stefan Hajnoczi
2012-03-26 12:07 ` [Qemu-devel] [PATCH 4/5] test: add test-qmp-commands to make check Stefan Hajnoczi
2012-03-26 12:07 ` [Qemu-devel] [PATCH 5/5] trace-events: Fix broken build caused by wrong format specifier Stefan Hajnoczi
2012-03-26 12:41 ` Andreas Färber
2012-03-26 12:48 ` Alon Levy [this message]
2012-03-26 21:10 ` [Qemu-devel] [PULL 0/5] Trivial patches for 20 to 26 March 2012 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=20120326124816.GB32389@garlic \
--to=alevy@redhat.com \
--cc=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
--cc=sw@weilnetz.de \
/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).