From: Gerd Hoffmann <kraxel@redhat.com>
To: Alon Levy <alevy@redhat.com>
Cc: blauwirbel@gmail.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v10 3/4] qxl: add QXL_IO_MONITORS_CONFIG_ASYNC
Date: Tue, 21 Aug 2012 12:34:34 +0200 [thread overview]
Message-ID: <5033643A.10805@redhat.com> (raw)
In-Reply-To: <1345544183-19192-3-git-send-email-alevy@redhat.com>
On 08/21/12 12:16, Alon Levy wrote:
> Revision bumped to 4 for new IO support, enabled for spice-server >=
> 0.11.1. New io enabled iff revision is 4. Revision can be set to 4, and
> defaults to 4, iff spice-server >= 0.11.1 && spice-protocol >=
> 0.12.0.
>
> This io calls the corresponding new spice api
> spice_qxl_monitors_config_async to let spice-server read a new guest set
> monitors config and notify the client.
>
> On migration reissue spice_qxl_monitors_config_async.
Applying: qxl: add QXL_IO_MONITORS_CONFIG_ASYNC
=== checkpatch complains ===
ERROR: space prohibited before open square bracket '['
#198: FILE: hw/qxl.c:2116:
+ .fields = (VMStateField []) {
ERROR: space prohibited before open square bracket '['
#211: FILE: hw/qxl.c:2148:
+ .subsections = (VMStateSubsection []) {
total: 2 errors, 0 warnings, 231 lines checked
next prev parent reply other threads:[~2012-08-21 10:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 10:16 [Qemu-devel] [PATCH v10 1/4] qxl/update_area_io: guest_bug on invalid parameters Alon Levy
2012-08-21 10:16 ` [Qemu-devel] [PATCH v10 2/4] qxl: disallow unknown revisions Alon Levy
2012-08-21 10:16 ` [Qemu-devel] [PATCH v10 3/4] qxl: add QXL_IO_MONITORS_CONFIG_ASYNC Alon Levy
2012-08-21 10:34 ` Gerd Hoffmann [this message]
2012-08-21 10:16 ` [Qemu-devel] [PATCH v10 4/4] configure: print spice-protocol and spice-server versions Alon Levy
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=5033643A.10805@redhat.com \
--to=kraxel@redhat.com \
--cc=alevy@redhat.com \
--cc=blauwirbel@gmail.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).