From: Anthony Liguori <anthony@codemonkey.ws>
To: Markus Armbruster <armbru@redhat.com>
Cc: Alon Levy <alevy@redhat.com>,
qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] Should new USB devices such as usb-ccid support legacy -usbdevice?
Date: Fri, 13 May 2011 11:47:43 -0500 [thread overview]
Message-ID: <4DCD60AF.5090107@codemonkey.ws> (raw)
In-Reply-To: <m3hb8y7e2y.fsf@blackfin.pond.sub.org>
On 05/13/2011 11:36 AM, Markus Armbruster wrote:
> When Gerd qdevified USB, he kept legacy -usbdevice working (commit
> 0958b4cc...). What about new USB devices? Should they get a legacy
> syntax, too?
>
> The only existing new device is usb-ccid, and it got one in commit
> 36707144.
What keeps -usbdevice from being a light wrapper to -device such that no
future code is needed for this?
I know some of the names are different but presumably we could use a map
for existing ones and pass through names for newer ones.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2011-05-13 16:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 16:36 [Qemu-devel] Should new USB devices such as usb-ccid support legacy -usbdevice? Markus Armbruster
2011-05-13 16:47 ` Anthony Liguori [this message]
2011-05-16 8:01 ` Gerd Hoffmann
2011-05-16 8:33 ` Markus Armbruster
2011-05-17 10:37 ` Kevin Wolf
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=4DCD60AF.5090107@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=alevy@redhat.com \
--cc=armbru@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.