From: Anthony Liguori <anthony@codemonkey.ws>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL 0/8] spice patch queue
Date: Tue, 01 Feb 2011 15:24:52 -0600 [thread overview]
Message-ID: <4D487A24.3080309@codemonkey.ws> (raw)
In-Reply-To: <1296123150-11599-1-git-send-email-kraxel@redhat.com>
On 01/27/2011 04:12 AM, Gerd Hoffmann wrote:
> Hi,
>
> This is the updated spice patch queue. Changes:
>
> * rebased against latest master, solved conflicts (trace-events).
> * added one more locking bugfix, found by Alon.
>
> please pull,
> Gerd
>
> The following changes since commit 0fad6efce5d3f18278b7239dece3c251b3e7c04d:
>
> target-arm: Fix loading of scalar value for Neon multiply-by-scalar (2011-01-26 14:30:24 +0100)
>
> are available in the git repository at:
> git://anongit.freedesktop.org/spice/qemu spice.v30.pull
>
> Alon Levy (1):
> spice: add chardev (v5)
>
Pulled. Thanks.
Although I expect that we'll continue working together in the future to
come up with a common guest agent infrastructure.
Regards,
Anthony Liguori
> Gerd Hoffmann (5):
> add migration state change notifiers
> spice/vnc: client migration.
> spice: MAINTAINERS update
> spice/qxl: zap spice 0.4 migration compatibility bits
> qxl: locking fixes
>
> Jiri Denemark (1):
> configure: Fix spice probe
>
> Marc-André Lureau (1):
> vnc/spice: fix "never" and "now" expire_time
>
> MAINTAINERS | 8 ++
> Makefile.objs | 2 +-
> configure | 6 +-
> hmp-commands.hx | 17 +++++
> hw/qxl.c | 83 ++++-------------------
> hw/qxl.h | 4 -
> migration.c | 28 ++++++++
> migration.h | 5 ++
> monitor.c | 31 ++++++++-
> qemu-char.c | 4 +
> qemu-config.c | 6 ++
> qemu-options.hx | 16 ++++-
> qmp-commands.hx | 35 ++++++++++
> spice-qemu-char.c | 190 +++++++++++++++++++++++++++++++++++++++++++++++++++++
> trace-events | 7 ++
> ui/qemu-spice.h | 7 ++
> ui/spice-core.c | 25 +++++++
> 17 files changed, 394 insertions(+), 80 deletions(-)
> create mode 100644 spice-qemu-char.c
>
>
>
next prev parent reply other threads:[~2011-02-01 22:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 10:12 [Qemu-devel] [PULL 0/8] spice patch queue Gerd Hoffmann
2011-01-27 10:12 ` [Qemu-devel] [PATCH 1/8] add migration state change notifiers Gerd Hoffmann
2011-01-27 10:12 ` [Qemu-devel] [PATCH 2/8] spice/vnc: client migration Gerd Hoffmann
2011-01-27 10:12 ` [Qemu-devel] [PATCH 3/8] spice: MAINTAINERS update Gerd Hoffmann
2011-01-27 10:12 ` [Qemu-devel] [PATCH 4/8] vnc/spice: fix "never" and "now" expire_time Gerd Hoffmann
2011-01-27 10:12 ` [Qemu-devel] [PATCH 5/8] spice/qxl: zap spice 0.4 migration compatibility bits Gerd Hoffmann
2011-01-27 10:12 ` [Qemu-devel] [PATCH 6/8] qxl: locking fixes Gerd Hoffmann
2011-01-27 10:12 ` [Qemu-devel] [PATCH 7/8] configure: Fix spice probe Gerd Hoffmann
2011-01-27 10:12 ` [Qemu-devel] [PATCH 8/8] spice: add chardev (v5) Gerd Hoffmann
2011-02-01 21:24 ` Anthony Liguori [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-12-17 13:04 [Qemu-devel] [PULL 0/8] spice patch queue Gerd Hoffmann
2012-12-18 23:49 ` Anthony Liguori
2012-10-08 10:49 Gerd Hoffmann
2012-10-12 16:18 ` 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=4D487A24.3080309@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).