qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Samuel Thibault <samuel.thibault@gnu.org>,
	Thomas Huth <thuth@redhat.com>,
	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: Fri, 5 Jan 2018 10:22:22 +0100	[thread overview]
Message-ID: <f0cc3ad6-ecdc-20f8-ed62-423477417ec1@redhat.com> (raw)
In-Reply-To: <87tvw0k9am.fsf@dusky.pond.sub.org>

On 05/01/2018 09:18, Markus Armbruster wrote:
>>> Would it be possible to make this automatic?  Before I could tell people
>>> "use -usbdevice braille to test braille", and now it would be
>>> "use -chardev braille,chardev=foobar -device usb-braille,chardev=foobar"
>> Maybe we can add "-braille" instead.  Something like this:
> More sugar, ugh!
> 
> What about giving braille property chardev a sensible default?
> Ideally in a self-documenting way, so that -device usb-braille,help
> shows the default.

That would mean automatically creating a back-end in a device's realize
property.  I'd rather avoid that, sugar is not bad per se.

Paolo

  reply	other threads:[~2018-01-05  9:22 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
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 [this message]
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=f0cc3ad6-ecdc-20f8-ed62-423477417ec1@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=armbru@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=samuel.thibault@gnu.org \
    --cc=thuth@redhat.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).