qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] usb-redir: Never return USB_RET_NAK for async handled packets
Date: Tue, 21 Aug 2012 10:36:27 +0200	[thread overview]
Message-ID: <5033488B.4090100@redhat.com> (raw)
In-Reply-To: <1345217228-9734-1-git-send-email-hdegoede@redhat.com>

On 08/17/12 17:27, Hans de Goede wrote:
> USB_RET_NAK is not a valid response for async handled packets (and will
> trigger an assert as such).
> 
> Also drop the warning when receiving a status of cancelled for packets not
> cancelled by qemu itself, this can happen when a device gets unredirected
> by the usbredir-host while transfers are pending.

Patch added to usb patch queue (2+3 from v1 too).

thanks,
  Gerd

      reply	other threads:[~2012-08-21  8:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-17 15:27 [Qemu-devel] [PATCH] usb-redir: Never return USB_RET_NAK for async handled packets Hans de Goede
2012-08-21  8:36 ` Gerd Hoffmann [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=5033488B.4090100@redhat.com \
    --to=kraxel@redhat.com \
    --cc=hdegoede@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).