From: Jack Un <jack.un@gmail.com>
To: qemu-devel@nongnu.org
Cc: kraxel@redhat.com, Jack Un <jack.un@gmail.com>
Subject: [Qemu-devel] [PATCH] Fix OHCI ISO TD state never being written back.
Date: Sat, 9 Aug 2014 23:34:36 +0300 [thread overview]
Message-ID: <1407616476-6181-2-git-send-email-jack.un@gmail.com> (raw)
In-Reply-To: <1407616476-6181-1-git-send-email-jack.un@gmail.com>
Signed-off-by: Jack Un <jack.un@gmail.com>
---
hw/usb/hcd-ohci.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/hw/usb/hcd-ohci.c b/hw/usb/hcd-ohci.c
index 13afdf5..cacf7b0 100644
--- a/hw/usb/hcd-ohci.c
+++ b/hw/usb/hcd-ohci.c
@@ -619,8 +619,8 @@ static inline int ohci_put_td(OHCIState *ohci,
static inline int ohci_put_iso_td(OHCIState *ohci,
dma_addr_t addr, struct ohci_iso_td *td)
{
- return put_dwords(ohci, addr, (uint32_t *)td, 4 ||
- put_words(ohci, addr + 16, td->offset, 8));
+ return put_dwords(ohci, addr, (uint32_t *)td, 4) ||
+ put_words(ohci, addr + 16, td->offset, 8);
}
static inline int ohci_put_hcca(OHCIState *ohci,
--
2.0.4
next prev parent reply other threads:[~2014-08-09 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 20:34 [Qemu-devel] [PATCH] Fix OHCI ISO TD state never being written back Jack Un
2014-08-09 20:34 ` Jack Un [this message]
2014-08-10 2:39 ` Gonglei
2014-08-28 8:32 ` Gerd Hoffmann
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=1407616476-6181-2-git-send-email-jack.un@gmail.com \
--to=jack.un@gmail.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).