From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PATCH 2/3] vnc: fix printf warnings showing up with VNC_DEBUG enabled.
Date: Fri, 20 Mar 2009 12:31:28 +0100 [thread overview]
Message-ID: <1237548689-8677-3-git-send-email-kraxel@redhat.com> (raw)
In-Reply-To: <1237548689-8677-1-git-send-email-kraxel@redhat.com>
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
---
vnc.c | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/vnc.c b/vnc.c
index f723d04..de9edea 100644
--- a/vnc.c
+++ b/vnc.c
@@ -957,7 +957,7 @@ long vnc_client_write_buf(VncState *vs, const uint8_t *data, size_t datalen)
} else
#endif /* CONFIG_VNC_TLS */
ret = send(vs->csock, data, datalen, 0);
- VNC_DEBUG("Wrote wire %p %d -> %ld\n", data, datalen, ret);
+ VNC_DEBUG("Wrote wire %p %zd -> %ld\n", data, datalen, ret);
return vnc_client_io_error(vs, ret, socket_error());
}
@@ -977,7 +977,7 @@ static long vnc_client_write_plain(VncState *vs)
long ret;
#ifdef CONFIG_VNC_SASL
- VNC_DEBUG("Write Plain: Pending output %p size %d offset %d. Wait SSF %d\n",
+ VNC_DEBUG("Write Plain: Pending output %p size %zd offset %zd. Wait SSF %d\n",
vs->output.buffer, vs->output.capacity, vs->output.offset,
vs->sasl.waitWriteSSF);
@@ -1062,7 +1062,7 @@ long vnc_client_read_buf(VncState *vs, uint8_t *data, size_t datalen)
} else
#endif /* CONFIG_VNC_TLS */
ret = recv(vs->csock, data, datalen, 0);
- VNC_DEBUG("Read wire %p %d -> %ld\n", data, datalen, ret);
+ VNC_DEBUG("Read wire %p %zd -> %ld\n", data, datalen, ret);
return vnc_client_io_error(vs, ret, socket_error());
}
@@ -1078,7 +1078,7 @@ long vnc_client_read_buf(VncState *vs, uint8_t *data, size_t datalen)
static long vnc_client_read_plain(VncState *vs)
{
int ret;
- VNC_DEBUG("Read plain %p size %d offset %d\n",
+ VNC_DEBUG("Read plain %p size %zd offset %zd\n",
vs->input.buffer, vs->input.capacity, vs->input.offset);
buffer_reserve(&vs->input, 4096);
ret = vnc_client_read_buf(vs, buffer_end(&vs->input), 4096);
--
1.6.1.3
next prev parent reply other threads:[~2009-03-20 11:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 11:31 [Qemu-devel] [PATCH 0/3] vnc patches Gerd Hoffmann
2009-03-20 11:31 ` [Qemu-devel] [PATCH 1/3] vnc: cleanup surface handling, fix screen corruption bug Gerd Hoffmann
2009-03-20 11:31 ` Gerd Hoffmann [this message]
2009-03-20 11:31 ` [Qemu-devel] [PATCH 3/3] vnc: throttle screen updates Gerd Hoffmann
2009-03-20 15:59 ` [Qemu-devel] [PATCH 0/3] vnc patches Anthony Liguori
-- strict thread matches above, loose matches on Subject: below --
2009-03-18 16:08 [Qemu-devel] [PATCH 2/3] vnc: fix printf warnings showing up with VNC_DEBUG enabled Gerd Hoffmann
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=1237548689-8677-3-git-send-email-kraxel@redhat.com \
--to=kraxel@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).