qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL 0/8] spice patch queue
Date: Tue, 18 Dec 2012 17:49:39 -0600	[thread overview]
Message-ID: <87623yyl7w.fsf@codemonkey.ws> (raw)
In-Reply-To: <1355749479-25470-1-git-send-email-kraxel@redhat.com>

Gerd Hoffmann <kraxel@redhat.com> writes:

>   Hi,
>
> This is the spice patch queue, bringing two bugfixes
> and chardev redirection over spice.

Pulled. Thanks.

Regards,

Anthony Liguori

>
> please pull,
>   Gerd
>
> The following changes since commit a8a826a3c3b8c8a1c4def0e9e22b46e78e6163a0:
>
>   exec: refactor cpu_restore_state (2012-12-16 08:35:24 +0000)
>
> are available in the git repository at:
>   git://anongit.freedesktop.org/spice/qemu spice.v66
>
> Gerd Hoffmann (1):
>       qxl: save qemu_create_displaysurface_from result
>
> Marc-André Lureau (6):
>       spice-qemu-char: write to chardev whatever amount it can read
>       spice-qemu-char: factor out CharDriverState creation
>       spice-qemu-char: add spiceport chardev
>       spice-qemu-char: keep a list of spice chardev
>       spice-qemu-char: register spicevmc ports during qemu_spice_init()
>       docs: add spice-port-fqdn.txt
>
> Uri Lublin (1):
>       qxl+vnc: register a vm state change handler for dummy spice_server
>
>  docs/spice-port-fqdn.txt |   19 ++++++++
>  hw/qxl-render.c          |   11 +++--
>  qemu-char.c              |    3 +
>  qemu-options.hx          |   13 ++++++
>  spice-qemu-char.c        |  107 ++++++++++++++++++++++++++++++++++++++--------
>  trace-events             |    1 +
>  ui/qemu-spice.h          |    4 ++
>  ui/spice-core.c          |    6 +++
>  8 files changed, 141 insertions(+), 23 deletions(-)
>  create mode 100644 docs/spice-port-fqdn.txt

  parent reply	other threads:[~2012-12-18 23:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-17 13:04 [Qemu-devel] [PULL 0/8] spice patch queue Gerd Hoffmann
2012-12-17 13:04 ` [Qemu-devel] [PATCH 1/8] qxl: save qemu_create_displaysurface_from result Gerd Hoffmann
2012-12-17 13:04 ` [Qemu-devel] [PATCH 2/8] qxl+vnc: register a vm state change handler for dummy spice_server Gerd Hoffmann
2012-12-17 13:04 ` [Qemu-devel] [PATCH 3/8] spice-qemu-char: write to chardev whatever amount it can read Gerd Hoffmann
2012-12-17 13:04 ` [Qemu-devel] [PATCH 4/8] spice-qemu-char: factor out CharDriverState creation Gerd Hoffmann
2012-12-17 13:04 ` [Qemu-devel] [PATCH 5/8] spice-qemu-char: add spiceport chardev Gerd Hoffmann
2012-12-17 13:04 ` [Qemu-devel] [PATCH 6/8] spice-qemu-char: keep a list of spice chardev Gerd Hoffmann
2012-12-17 13:04 ` [Qemu-devel] [PATCH 7/8] spice-qemu-char: register spicevmc ports during qemu_spice_init() Gerd Hoffmann
2012-12-17 13:04 ` [Qemu-devel] [PATCH 8/8] docs: add spice-port-fqdn.txt Gerd Hoffmann
2012-12-18 23:49 ` Anthony Liguori [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-10-08 10:49 [Qemu-devel] [PULL 0/8] spice patch queue Gerd Hoffmann
2012-10-12 16:18 ` Anthony Liguori
2011-01-27 10:12 Gerd Hoffmann
2011-02-01 21:24 ` Anthony Liguori
2011-01-24 16:20 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=87623yyl7w.fsf@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=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).