qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Samuel Brian <sam.brian@accelerated.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] usb-host: support devices with sparse/non-sequential USB interfaces
Date: Tue, 13 Jun 2017 12:22:55 +0200	[thread overview]
Message-ID: <1497349375.8068.3.camel@redhat.com> (raw)
In-Reply-To: <dc2d2f2f-0c82-fa8f-9da1-b183fc203110@accelerated.com>

On Tue, 2017-06-13 at 14:17 +1000, Samuel Brian wrote:
> This change allows sparse USB interface numbering.
> Instead of only claiming the interfaces in the range reported by the
> USB
> device through bNumInterfaces, QEMU attempts to claim all possible
> interfaces.

Patch looks good but fails to apply.  Thunderbird wrapped lines and
corrupted the patch.

Please resend using "git send-email" to avoid that.

thanks,
  Gerd

  reply	other threads:[~2017-06-13 10:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13  4:17 [Qemu-devel] [PATCH] usb-host: support devices with sparse/non-sequential USB interfaces Samuel Brian
2017-06-13 10:22 ` Gerd Hoffmann [this message]
2017-06-13 23:48   ` Samuel Brian

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=1497349375.8068.3.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sam.brian@accelerated.com \
    /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).