From: Anthony Liguori <anthony@codemonkey.ws>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCHES for 1.0] various spice usb-redir integration patches
Date: Mon, 28 Nov 2011 16:34:08 -0600 [thread overview]
Message-ID: <4ED40C60.9010901@codemonkey.ws> (raw)
In-Reply-To: <1321694567-2855-1-git-send-email-hdegoede@redhat.com>
On 11/19/2011 03:22 AM, Hans de Goede wrote:
> Hi All,
>
> Sorry for sending these in so late, I send most of them in before a long time
> ago, but then they got stuck on waiting for the big chardev rewrite. Since it
> seems clear now that the big chardev rewrite won't happen before 1.0, I would
> like to get these into 1.0 as is.
Applied all. Thanks.
Regards,
Anthony Liguori
>
> Thanks& Regards,
>
> Hans
>
>
>
prev parent reply other threads:[~2011-11-28 22:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 9:22 [Qemu-devel] [PATCHES for 1.0] various spice usb-redir integration patches Hans de Goede
2011-11-19 9:22 ` [Qemu-devel] [PATCH 1/5] qemu-char: rename qemu_chr_event to qemu_chr_be_event and make it public Hans de Goede
2011-11-19 9:22 ` [Qemu-devel] [PATCH 2/5] spice-qemu-char: Generate chardev open/close events Hans de Goede
2011-11-19 9:22 ` [Qemu-devel] [PATCH 3/5] usb-redir: Call qemu_chr_fe_open/close Hans de Goede
2011-11-19 9:22 ` [Qemu-devel] [PATCH 4/5] usb-redir: Device disconnect + re-connect robustness fixes Hans de Goede
2011-11-19 9:22 ` [Qemu-devel] [PATCH 5/5] usb-redir: Don't try to write to the chardev after a close event Hans de Goede
2011-11-21 21:05 ` [Qemu-devel] [PATCHES for 1.0] various spice usb-redir integration patches Anthony Liguori
2011-11-22 16:36 ` Gerd Hoffmann
2011-11-28 22:34 ` Anthony Liguori [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=4ED40C60.9010901@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=hdegoede@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.