From: Gerd Hoffmann <kraxel@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v1 0/3] Convert VNC server to QIOChannel
Date: Tue, 15 Dec 2015 11:35:53 +0100 [thread overview]
Message-ID: <1450175753.24446.2.camel@redhat.com> (raw)
In-Reply-To: <1447872780-2229-1-git-send-email-berrange@redhat.com>
On Mi, 2015-11-18 at 18:52 +0000, Daniel P. Berrange wrote:
> This is an update of patches previously shown in an RFC posting
>
> RFC: https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg00829.html
>
> This series depends on the previously posted series:
>
> "[PATCH v3 0/9] Introduce I/O channels framework"
>
> This short series converts the VNC server to use the new
> QIOChannel framework. This removes all the websocket protocol
> code from the VNC server and further simplifies the TLS
> handling in the VNC server
>
> The conversion has been tested against the virt-viewer/
> remote-viewer programs in the various TLS modes, and also
> against the noVNC proxy websockets client with and without
> TLS support.
Looks good to me. In case you want send the pull request yourself:
Reviewed-by: Gerd Hoffmann <kraxel@redhat.com>
Otherwise ping me when the depending patch series is merged.
thanks,
Gerd
prev parent reply other threads:[~2015-12-15 10:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 18:52 [Qemu-devel] [PATCH v1 0/3] Convert VNC server to QIOChannel Daniel P. Berrange
2015-11-18 18:52 ` [Qemu-devel] [PATCH v1 1/3] ui: convert VNC server to use QIOChannelSocket Daniel P. Berrange
2015-11-18 18:52 ` [Qemu-devel] [PATCH v1 2/3] ui: convert VNC server to use QIOChannelTLS Daniel P. Berrange
2015-11-18 18:53 ` [Qemu-devel] [PATCH v1 3/3] ui: convert VNC server to use QIOChannelWebsock Daniel P. Berrange
2015-12-15 10:35 ` 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=1450175753.24446.2.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=berrange@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).