qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	Samuel Thibault <samuel.thibault@gnu.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	kraxel@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] usb: Remove legacy -usbdevice option
Date: Mon, 8 Jan 2018 08:23:55 +0100	[thread overview]
Message-ID: <351493cf-fa56-491c-c646-49727e6611ed@redhat.com> (raw)
In-Reply-To: <64a364f0-3dc0-87c4-f0b0-a79365032a8e@redhat.com>

On 04.01.2018 18:10, Paolo Bonzini wrote:
> On 04/01/2018 16:59, Thomas Huth wrote:
>>
>> But instead of introducing a new "-braille" parameter, maybe we should
>> rather keep some of the convenience "-usbdevice" possibilities around?
>> E.g. keep "-usbdevice braille", "-usbdevice mouse", etc. but remove
>> things like "-usbdevice serial" and "-usbdevice host" where the code is
>> rather ugly and the user do not gain much in comparison to "-device" ?
> 
> That would work too.  But I'm not sure why keep all the usbdevice
> infrastructure when we can do the same (at the price of a small cmdline
> incompatibility) with only 50 lines of code.

I'm just afraid that we will end up with more new parameters in the end
than just "-braille" - or do we feel confident enough that "-usbdevice
braille" is the only one that would need a sugared replacement?

 Thomas

  reply	other threads:[~2018-01-08  7:24 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04 13:15 [Qemu-devel] [PATCH v2] usb: Remove legacy -usbdevice option Thomas Huth
2018-01-04 14:09 ` Samuel Thibault
2018-01-04 14:12   ` Thomas Huth
2018-01-04 14:15     ` Samuel Thibault
2018-01-04 14:21       ` Samuel Thibault
2018-01-04 15:19         ` Paolo Bonzini
2018-01-04 15:24           ` Samuel Thibault
2018-01-04 15:28             ` Paolo Bonzini
2018-01-04 15:32               ` Samuel Thibault
2018-01-04 15:33                 ` Paolo Bonzini
2018-01-04 15:35                 ` Thomas Huth
2018-01-04 15:47                   ` Paolo Bonzini
2018-01-04 15:52                     ` Peter Maydell
2018-01-05  8:24                       ` Markus Armbruster
2018-01-04 15:56                     ` Samuel Thibault
2018-01-04 17:11                       ` Paolo Bonzini
2018-01-04 17:45                         ` Samuel Thibault
2018-01-04 17:57                           ` Paolo Bonzini
2018-01-04 18:02                             ` Samuel Thibault
2018-01-08  7:43                             ` Thomas Huth
2018-01-09  9:57                               ` Paolo Bonzini
2018-01-04 15:59                     ` Thomas Huth
2018-01-04 17:10                       ` Paolo Bonzini
2018-01-08  7:23                         ` Thomas Huth [this message]
2018-01-09  9:58                           ` Paolo Bonzini
2018-01-09 11:00                             ` Thomas Huth
2018-01-09 11:17                               ` Paolo Bonzini
2018-01-09 11:57                                 ` Thomas Huth
2018-01-09 13:45                                   ` Gerd Hoffmann
2018-01-04 15:42               ` Thomas Huth
2018-01-05  8:18           ` Markus Armbruster
2018-01-05  9:22             ` Paolo Bonzini
2018-01-05 10:09               ` Markus Armbruster

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=351493cf-fa56-491c-c646-49727e6611ed@redhat.com \
    --to=thuth@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=samuel.thibault@gnu.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).