From: Hans de Goede <hdegoede@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/4] RFC: uhci: various cleanups
Date: Thu, 18 Oct 2012 16:08:55 +0200 [thread overview]
Message-ID: <1350569339-2811-1-git-send-email-hdegoede@redhat.com> (raw)
The main reason this is RFC is because it applies on top of my previous 2 RFC
series. Review / comments welcome, then I can work them into the final version
(which I will send when the other 2 series are done).
Regards,
Hans
next reply other threads:[~2012-10-18 14:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 14:08 Hans de Goede [this message]
2012-10-18 14:08 ` [Qemu-devel] [PATCH 1/4] usb: Enforce iso endpoints never returing USB_RET_ASYNC Hans de Goede
2012-10-18 14:08 ` [Qemu-devel] [PATCH 2/4] uhci: No need to handle async completion of isoc packets Hans de Goede
2012-10-18 14:08 ` [Qemu-devel] [PATCH 3/4] uhci: cleanup: Add an unlink call to uhci_async_cancel() Hans de Goede
2012-10-18 14:08 ` [Qemu-devel] [PATCH 4/4] uhci: Don't retry on error 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=1350569339-2811-1-git-send-email-hdegoede@redhat.com \
--to=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 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).