From: Anthony Liguori <anthony@codemonkey.ws>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH 4/8] vnc: fix numlock+capslock tracking
Date: Fri, 28 Jan 2011 14:11:44 -0600 [thread overview]
Message-ID: <4D432300.6030005@codemonkey.ws> (raw)
In-Reply-To: <4D431FDB.1010003@redhat.com>
On 01/28/2011 01:58 PM, Gerd Hoffmann wrote:
> Hi,
>
>> This should be 1/8 or 2/8 in the series.
>>
>> Also, perhaps these four could go in 0.14? The USB device are really
>> much more usable (especially the keyboard) with them.
>
> IMHO the whole series should go to 0.14, otherwise the remote wakeup
> support added recently will simply not play together with migration.
Yeah, and for something as core as "add migration" support, I'm inclined
to agree. I'm amazed this hasn't been a bigger problem to date.
Regards,
Anthony Liguori
> cheers,
> Gerd
>
next prev parent reply other threads:[~2011-01-28 20:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 16:30 [Qemu-devel] [PULL 0/8] usb patch queue Gerd Hoffmann
2011-01-24 16:30 ` [Qemu-devel] [PATCH 1/8] add event queueing to USB HID Gerd Hoffmann
2011-01-24 16:30 ` [Qemu-devel] [PATCH 2/8] usb keyboard: add event event queue Gerd Hoffmann
2011-01-24 16:30 ` [Qemu-devel] [PATCH 3/8] usb hid: move head+n to common struct Gerd Hoffmann
2011-01-24 16:30 ` [Qemu-devel] [PATCH 4/8] vnc: fix numlock+capslock tracking Gerd Hoffmann
2011-01-28 13:36 ` [Qemu-devel] " Paolo Bonzini
2011-01-28 19:58 ` Gerd Hoffmann
2011-01-28 20:11 ` Anthony Liguori [this message]
2011-01-24 16:30 ` [Qemu-devel] [PATCH 5/8] usb core: add migration support Gerd Hoffmann
2011-01-24 16:30 ` [Qemu-devel] [PATCH 6/8] usb hub: " Gerd Hoffmann
2011-01-24 16:30 ` [Qemu-devel] [PATCH 7/8] usb hid: " Gerd Hoffmann
2011-01-24 16:30 ` [Qemu-devel] [PATCH 8/8] usb-bus: use snprintf Gerd Hoffmann
2011-02-17 20:00 ` [Qemu-devel] [PULL 0/8] usb patch queue Anthony Liguori
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=4D432300.6030005@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kraxel@redhat.com \
--cc=pbonzini@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).