From: Gerd Hoffmann <kraxel@redhat.com>
To: Lin Ma <lma@suse.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] usb: Use usb_bus_find(-1) instead of usb_enabled() in usb_device_add/usb_device_del
Date: Tue, 16 Jun 2015 15:31:45 +0200 [thread overview]
Message-ID: <1434461505.15692.61.camel@redhat.com> (raw)
In-Reply-To: <1433404534-12003-1-git-send-email-lma@suse.com>
On Do, 2015-06-04 at 15:55 +0800, Lin Ma wrote:
> Without usb=on machine option, usb_device_add/usb_device_del don't work,
> Even if there are virtual usb controllers presented.
If you use -device to add your usb host controllers, you should likewise
use -device (or device_add monitor cmd) to add your usb devices.
-usbdevice is legacy syntax and only there for backward compatibility.
cheers,
Gerd
prev parent reply other threads:[~2015-06-16 13:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 7:55 [Qemu-devel] [PATCH] usb: Use usb_bus_find(-1) instead of usb_enabled() in usb_device_add/usb_device_del Lin Ma
2015-06-16 13:31 ` 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=1434461505.15692.61.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=lma@suse.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).