From: Gerd Hoffmann <kraxel@redhat.com>
To: Alon Levy <alevy@redhat.com>
Cc: hdegoede@redhat.com, qemu-devel@nongnu.org, spice-devel@freedesktop.org
Subject: Re: [Qemu-devel] [PATCH 0/3] client monitors config support
Date: Thu, 13 Sep 2012 08:43:47 +0200 [thread overview]
Message-ID: <505180A3.6060005@redhat.com> (raw)
In-Reply-To: <1347455618-2465-1-git-send-email-alevy@redhat.com>
On 09/12/12 15:13, Alon Levy wrote:
> - no addition of guest capabilities, use interrupt mask instead, ignore
> 0 or ~0 that are set by current windows driver.
> - use crc to solve possible write while read.
> - limit heads to 64, statically allocated on rom by host.
> - some misc trace fixes.
Patch series added to spice patch queue.
thanks,
Gerd
prev parent reply other threads:[~2012-09-13 6:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 13:13 [Qemu-devel] [PATCH 0/3] client monitors config support Alon Levy
2012-09-12 13:13 ` [Qemu-devel] [PATCH 1/3] hw/qxl: tracing fixes Alon Levy
2012-09-12 13:13 ` [Qemu-devel] [PATCH 2/3] qxl: add trace-event for QXL_IO_LOG Alon Levy
2012-09-12 13:13 ` [Qemu-devel] [PATCH 3/3] hw/qxl: support client monitor configuration via device Alon Levy
2012-09-13 6:43 ` 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=505180A3.6060005@redhat.com \
--to=kraxel@redhat.com \
--cc=alevy@redhat.com \
--cc=hdegoede@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=spice-devel@freedesktop.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).