From: Gerd Hoffmann <kraxel@redhat.com>
To: Alon Levy <alevy@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] qxl: unbreak after memory API conversion
Date: Wed, 10 Aug 2011 17:29:45 +0200 [thread overview]
Message-ID: <4E42A3E9.40401@redhat.com> (raw)
In-Reply-To: <1312923215-11824-1-git-send-email-alevy@redhat.com>
On 08/09/11 22:53, Alon Levy wrote:
> Break is only noticable with newer spice-server library (0.8.2 release
> or 0.9.0 and newer on master branch).
>
> ioport_write's val was changed from uint32_t to uint64_t, this
> broke two printfs. Use PRId64 instead of %d.
Added to the spice patch queue.
thanks,
Gerd
prev parent reply other threads:[~2011-08-10 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 20:53 [Qemu-devel] [PATCH 1/2] qxl: unbreak after memory API conversion Alon Levy
2011-08-09 20:53 ` [Qemu-devel] [PATCH 2/2] ui/spice-core: report version in 'info spice' Alon Levy
2011-08-10 6:54 ` Gerd Hoffmann
2011-08-10 7:43 ` Alon Levy
2011-08-10 8:10 ` Gerd Hoffmann
2011-08-10 8:32 ` Alon Levy
2011-08-10 15:10 ` Gerd Hoffmann
2011-08-10 15:29 ` Gerd Hoffmann [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=4E42A3E9.40401@redhat.com \
--to=kraxel@redhat.com \
--cc=alevy@redhat.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).