From: Thomas Huth <thuth@redhat.com>
To: Hans Petter Selasky <hps@selasky.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU XHCI support (FreeBSD)
Date: Tue, 23 Aug 2016 00:03:14 +0200 [thread overview]
Message-ID: <fba3ba87-5218-56f4-0b49-1ba9cdf2a99e@redhat.com> (raw)
In-Reply-To: <f4fd0eab-2cdb-0ca4-9ef1-08cf50b356a8@selasky.org>
On 22.08.2016 20:15, Hans Petter Selasky wrote:
> Hi,
>
> I'm currently testing QEMUs XHCI support with FreeBSD and found some
> bugs in FreeBSDs XHCI aswell as QEMUs XHCI.
>
> 1) QEMU falsely reports a remainder of 8 bytes on TR_SETUP. This patch
> fixes it. Can it be upstreamed?
Hi Hans,
please make sure to send patches with a proper "Signed-off-by" line,
otherwise they can't be accepted. See the following URL for details:
http://wiki.qemu.org/Contribute/SubmitAPatch#Patch_emails_must_include_a_Signed-off-by:_line
Regards,
Thomas
prev parent reply other threads:[~2016-08-22 22:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <90075d89-5c04-d419-9f98-7d9bc70555d3@selasky.org>
2016-08-22 18:15 ` [Qemu-devel] QEMU XHCI support (FreeBSD) Hans Petter Selasky
2016-08-22 22:03 ` Thomas Huth [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=fba3ba87-5218-56f4-0b49-1ba9cdf2a99e@redhat.com \
--to=thuth@redhat.com \
--cc=hps@selasky.org \
--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).