qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Apfelbaum <marcel.a@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: aliguori@us.ibm.com, mst@redhat.com, qemu-devel@nongnu.org,
	afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH v3 0/3] qemu-help: improve -device command line help
Date: Mon, 29 Jul 2013 15:37:27 +0300	[thread overview]
Message-ID: <1375101447.18120.18.camel@localhost.localdomain> (raw)
In-Reply-To: <51F660D6.9090301@redhat.com>

On Mon, 2013-07-29 at 14:32 +0200, Paolo Bonzini wrote:
> Il 29/07/2013 14:11, Marcel Apfelbaum ha scritto:
> > Running qemu with "-device ?" option returns ~145 lines.
> > It is hard to manage understanding the output.
> > 
> > Theses patches aim to partially solve the problem by dividing the devices
> > into logical categories like "Network/Display/..." and sorting them by it.
> > 
> > Categories:
> > Assembly   - hosts/hubs/... 
> > ...
> > (All others are self explanatory)
> 
> Can we rename it to something like "bridge" that you can print as
> "Controller/Bridge/Hub"?
Sure
> 
> Paolo

      reply	other threads:[~2013-07-29 12:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29 12:11 [Qemu-devel] [PATCH v3 0/3] qemu-help: improve -device command line help Marcel Apfelbaum
2013-07-29 12:11 ` [Qemu-devel] [PATCH v3 1/3] hw: import bitmap operations in qdev-core header Marcel Apfelbaum
2013-07-29 12:11 ` [Qemu-devel] [PATCH v3 2/3] qemu-help: Sort devices by logical functionality Marcel Apfelbaum
2013-07-29 12:28   ` Michael S. Tsirkin
2013-07-29 12:36     ` Marcel Apfelbaum
2013-07-29 12:42       ` Michael S. Tsirkin
2013-07-29 12:52         ` Marcel Apfelbaum
2013-07-29 12:30   ` Marcel Apfelbaum
2013-07-29 12:11 ` [Qemu-devel] [PATCH v3 3/3] devices: Associate devices to their logical category Marcel Apfelbaum
2013-07-29 12:32 ` [Qemu-devel] [PATCH v3 0/3] qemu-help: improve -device command line help Paolo Bonzini
2013-07-29 12:37   ` Marcel Apfelbaum [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=1375101447.18120.18.camel@localhost.localdomain \
    --to=marcel.a@redhat.com \
    --cc=afaerber@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@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).