From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: lersek@redhat.com, Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PATCH 0/2] xhci: fix control transfer event reporting
Date: Tue, 5 May 2015 11:59:11 +0200 [thread overview]
Message-ID: <1430819953-12931-1-git-send-email-kraxel@redhat.com> (raw)
Hi,
Laszlos fix unfortunaly had unwanted side effects, so we have
to take a different approach to fix the issue at hand.
please review,
Gerd
Gerd Hoffmann (2):
Revert "xhci: generate a Transfer Event for each Transfer TRB with the
IOC bit set"
xhci: fix events for setup trb.
hw/usb/hcd-xhci.c | 23 +++++++++++------------
1 file changed, 11 insertions(+), 12 deletions(-)
--
1.8.3.1
next reply other threads:[~2015-05-05 9:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 9:59 Gerd Hoffmann [this message]
2015-05-05 9:59 ` [Qemu-devel] [PATCH 1/2] Revert "xhci: generate a Transfer Event for each Transfer TRB with the IOC bit set" Gerd Hoffmann
2015-05-05 9:59 ` [Qemu-devel] [PATCH 2/2] xhci: fix events for setup trb Gerd Hoffmann
2015-05-05 10:59 ` [Qemu-devel] [PATCH 0/2] xhci: fix control transfer event reporting Laszlo Ersek
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=1430819953-12931-1-git-send-email-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=lersek@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).