From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PULL for-2.7 0/3] vnc: fixes for "-vnc none".
Date: Wed, 3 Aug 2016 17:35:19 +0200 [thread overview]
Message-ID: <1470238522-28094-1-git-send-email-kraxel@redhat.com> (raw)
Hi,
vnc patch queue, with three patches fixing "-vnc none" with
connects via monitor fd passing.
cheers,
Gerd
The following changes since commit cc0100f464c94bf80ad36cd432f4a1ed58126b60:
MAINTAINERS: Update the Xilinx maintainers (2016-08-01 15:31:32 +0100)
are available in the git repository at:
git://git.kraxel.org/qemu tags/pull-vnc-20160803-1
for you to fetch changes up to 12e29b1682e0a50ed57c324152addb585ae5ce69:
vnc: ensure connection sharing/limits is always configured (2016-08-03 15:06:32 +0200)
----------------------------------------------------------------
vnc: fixes for "-vnc none".
----------------------------------------------------------------
Daniel P. Berrange (3):
vnc: don't crash getting server info if lsock is NULL
vnc: fix crash when vnc_server_info_get has an error
vnc: ensure connection sharing/limits is always configured
ui/vnc.c | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
next reply other threads:[~2016-08-03 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 15:35 Gerd Hoffmann [this message]
2016-08-03 15:35 ` [Qemu-devel] [PULL 1/3] vnc: don't crash getting server info if lsock is NULL Gerd Hoffmann
2016-08-03 15:35 ` [Qemu-devel] [PULL 2/3] vnc: fix crash when vnc_server_info_get has an error Gerd Hoffmann
2016-08-03 15:35 ` [Qemu-devel] [PULL 3/3] vnc: ensure connection sharing/limits is always configured Gerd Hoffmann
2016-08-04 9:24 ` [Qemu-devel] [PULL for-2.7 0/3] vnc: fixes for "-vnc none" 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=1470238522-28094-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).