From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PATCH 0/2] spice fixes.
Date: Fri, 15 Oct 2010 11:31:35 +0200 [thread overview]
Message-ID: <1287135097-8914-1-git-send-email-kraxel@redhat.com> (raw)
Hi,
This patch series brings two bug fixes for spice.
The patches are also available in the git repository at:
git://anongit.freedesktop.org/spice/qemu bugfix.1
please pull,
Gerd
Gerd Hoffmann (1):
spice display: replace private lock with qemu mutex.
Hans de Goede (1):
spice-core: fix watching for write events
ui/spice-core.c | 2 +-
ui/spice-display.c | 22 +++++++++-------------
ui/spice-display.h | 1 -
3 files changed, 10 insertions(+), 15 deletions(-)
next reply other threads:[~2010-10-15 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 9:31 Gerd Hoffmann [this message]
2010-10-15 9:31 ` [Qemu-devel] [PATCH 1/2] spice-core: fix watching for write events Gerd Hoffmann
2010-10-15 9:31 ` [Qemu-devel] [PATCH 2/2] spice display: replace private lock with qemu mutex 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=1287135097-8914-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).