From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PULL for-2.1 0/2] vnc: fix two vnc update issues.
Date: Thu, 24 Jul 2014 10:28:04 +0200 [thread overview]
Message-ID: <1406190486-16026-1-git-send-email-kraxel@redhat.com> (raw)
Hi,
Here are two vnc update bugfixes, found by code review while hunting
down a issue with vnc updates not being sent to the client. The
original issue has not been root-caused yet, it is also not clear
whenever qemu is at fault at all or whenever the vnc updates are
stuck somewhere else (kernel network stack). The bugs found are
for real nevertheless, and here are the fixes.
please pull,
Gerd
The following changes since commit f368c33d5ab09dd5656924185cd975b11838cd25:
Update version for v2.1.0-rc3 release (2014-07-22 18:17:03 +0100)
are available in the git repository at:
git://git.kraxel.org/qemu tags/pull-vnc-20140724-1
for you to fetch changes up to 832932a6f17983a3167ae9da6fe54a245a30758e:
vnc update fix (2014-07-24 10:14:34 +0200)
----------------------------------------------------------------
vnc: fix two vnc update issues.
----------------------------------------------------------------
Gerd Hoffmann (1):
vnc update fix
Stephan Kulow (1):
fix full frame updates for VNC clients
ui/vnc.c | 5 ++++-
ui/vnc.h | 1 +
2 files changed, 5 insertions(+), 1 deletion(-)
next reply other threads:[~2014-07-24 8:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 8:28 Gerd Hoffmann [this message]
2014-07-24 8:28 ` [Qemu-devel] [PULL for-2.1 1/2] fix full frame updates for VNC clients Gerd Hoffmann
2014-07-24 12:30 ` Andreas Färber
2014-07-24 13:45 ` Stephan Kulow
2014-07-24 13:57 ` Andreas Färber
2014-07-24 8:28 ` [Qemu-devel] [PULL for-2.1 2/2] vnc update fix Gerd Hoffmann
2014-07-24 11:48 ` [Qemu-devel] [PULL for-2.1 0/2] vnc: fix two vnc update issues Peter Maydell
2014-07-24 12:20 ` Andreas Färber
2014-07-24 14:10 ` Gerd Hoffmann
2014-07-24 14:22 ` Peter Maydell
2014-07-25 7:45 ` Gerd Hoffmann
2014-07-25 11:52 ` Peter Maydell
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=1406190486-16026-1-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).