From: Hans de Goede <hdegoede@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Amit Shah <amit.shah@redhat.com>,
Hans de Goede <hdegoede@redhat.com>,
qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/7] Spice / usb-redir chardev flowcontrol patches v3
Date: Thu, 28 Mar 2013 14:28:10 +0100 [thread overview]
Message-ID: <1364477297-2083-1-git-send-email-hdegoede@redhat.com> (raw)
I think you may already have these in a local branch, but since I've not
yet seen a pull request for them, here is another resend.
Here is v3 of the series adding watch support to the spicevmc chardev backend
and flowcontrol support to the usb-redir device. It also includes a few
virtio-consoled bugfixes which were found during the development of this
series.
Changes in v2:
-Address Amit's review of "[PATCH 2/8] virtio-console: Remove any pending
watches on close"
-Drop 2 spice-qemu-char cleanup patches as Gerd has added them to his v5 series
-Add a (forward ported) patch from Alon Levy to fix a long standing
spice-qemu-char migration issue in a way which should be acceptable upstream
Changes in v3:
-Rebased on top of latest master (some trivial manual conflict resolution)
-Dropped Alon's patch for the spice-qemu-char migration issue, this is fixed
differently in another series which is already par of the latest master
-Add a new patch:
usb-serial: Remove double call to qemu_chr_add_handlers( NULL )
-Fixed a checkpatch issue in:
usb-redir: Add flow control support
Regards,
Hans
Alon Levy (1):
spice-qemu-char: Remove intermediate buffer
Hans de Goede (6):
virtio-console: Also throttle when less was written then requested
virtio-console: Remove any pending watches on close
spice-qemu-char: Remove #ifdef-ed code for old spice-server compat
spice-qemu-char: Add watch support
usb-redir: Add flow control support
usb-serial: Remove double call to qemu_chr_add_handlers( NULL )
hw/usb/dev-serial.c | 9 -----
hw/usb/redirect.c | 33 +++++++++++++++-
hw/virtio-console.c | 29 ++++++++++++--
spice-qemu-char.c | 106 +++++++++++++++++++++++++++++++++-------------------
4 files changed, 124 insertions(+), 53 deletions(-)
--
1.8.1.4
next reply other threads:[~2013-03-28 13:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 13:28 Hans de Goede [this message]
2013-03-28 13:28 ` [Qemu-devel] [PATCH 1/7] virtio-console: Also throttle when less was written then requested Hans de Goede
2013-03-29 9:31 ` Amit Shah
2013-04-01 16:00 ` Hans de Goede
2013-04-02 10:40 ` Amit Shah
2013-04-02 17:32 ` Hans de Goede
2013-03-28 13:28 ` [Qemu-devel] [PATCH 2/7] virtio-console: Remove any pending watches on close Hans de Goede
2013-03-28 13:28 ` [Qemu-devel] [PATCH 3/7] spice-qemu-char: Remove #ifdef-ed code for old spice-server compat Hans de Goede
2013-03-28 13:28 ` [Qemu-devel] [PATCH 4/7] spice-qemu-char: Add watch support Hans de Goede
2013-03-28 13:28 ` [Qemu-devel] [PATCH 5/7] spice-qemu-char: Remove intermediate buffer Hans de Goede
2013-03-28 13:28 ` [Qemu-devel] [PATCH 6/7] usb-redir: Add flow control support Hans de Goede
2013-03-28 13:28 ` [Qemu-devel] [PATCH 7/7] usb-serial: Remove double call to qemu_chr_add_handlers( NULL ) Hans de Goede
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=1364477297-2083-1-git-send-email-hdegoede@redhat.com \
--to=hdegoede@redhat.com \
--cc=amit.shah@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 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).