From: Amit Shah <amit.shah@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu list <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 1/4] qdev: Add a description field for qdev properties for documentation
Date: Tue, 28 Sep 2010 19:32:23 +0530 [thread overview]
Message-ID: <20100928140223.GJ2636@amit-laptop.redhat.com> (raw)
In-Reply-To: <m3eiceascd.fsf@blackfin.pond.sub.org>
On (Tue) Sep 28 2010 [15:52:02], Markus Armbruster wrote:
> Amit Shah <amit.shah@redhat.com> writes:
>
> > Add a 'description' along with each qdev property to document the input
> > each qdev property takes.
> [...]
> > diff --git a/hw/qdev.c b/hw/qdev.c
> > index 35858cb..b415025 100644
> > --- a/hw/qdev.c
> > +++ b/hw/qdev.c
> > @@ -188,7 +188,8 @@ int qdev_device_help(QemuOpts *opts)
> > if (!prop->info->parse) {
> > continue; /* no way to set it, don't show */
> > }
> > - error_printf("%s.%s=%s\n", info->name, prop->name, prop->info->name);
> > + error_printf("%s.%s=%s, %s\n", info->name, prop->name,
> > + prop->info->name, prop->desc ?: "");
> > }
> > return 1;
> > }
>
> This is the only patch hunk that isn't about defining or initializing
> the new member desc, isn't it?
Right; the other hunks just add the new desc field for all the callers.
Amit
next prev parent reply other threads:[~2010-09-28 14:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 12:36 [Qemu-devel] [PATCH 0/4] First steps towards documenting qdev devices/options Amit Shah
2010-09-15 12:36 ` [Qemu-devel] [PATCH 1/4] qdev: Add a description field for qdev properties for documentation Amit Shah
2010-09-28 13:52 ` Markus Armbruster
2010-09-28 14:02 ` Amit Shah [this message]
2010-09-15 12:36 ` [Qemu-devel] [PATCH 2/4] virtio-serial: Add description fields for qdev properties Amit Shah
2010-09-28 13:48 ` Markus Armbruster
2010-09-28 14:00 ` Amit Shah
2010-09-15 12:36 ` [Qemu-devel] [PATCH 3/4] net.h: Add description fields for qdev properites Amit Shah
2010-09-15 12:36 ` [Qemu-devel] [PATCH 4/4] block_int.h: Provide documentation for common block qdev properties Amit Shah
2010-09-28 14:36 ` [Qemu-devel] [PATCH 0/4] First steps towards documenting qdev devices/options Markus Armbruster
-- strict thread matches above, loose matches on Subject: below --
2010-11-25 17:31 [Qemu-devel] [PATCH 0/4] [RESEND] [REBASE] Auto-document qdev devices Amit Shah
2010-11-25 17:31 ` [Qemu-devel] [PATCH 1/4] qdev: Add a description field for qdev properties for documentation Amit Shah
2011-01-04 12:22 [Qemu-devel] [PATCH 0/4] [RESEND] [REBASE] Auto-document qdev devices Amit Shah
2011-01-04 12:22 ` [Qemu-devel] [PATCH 1/4] qdev: Add a description field for qdev properties for documentation Amit Shah
2011-01-10 14:31 ` Markus Armbruster
2011-01-11 0:01 ` Chris Krumme
2011-01-11 5:16 ` Amit Shah
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=20100928140223.GJ2636@amit-laptop.redhat.com \
--to=amit.shah@redhat.com \
--cc=armbru@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).