From: Markus Armbruster <armbru@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org, eblake@redhat.com,
marcandre.lureau@redhat.com, pbonzini@redhat.com,
berrange@redhat.com, mst@redhat.com,
marcel.apfelbaum@gmail.com, jiri@resnulli.us, jsnow@redhat.com
Subject: Re: [PATCH 1/6] qapi/char: Supply missing member documentation
Date: Fri, 09 Aug 2024 11:11:59 +0200 [thread overview]
Message-ID: <875xsakqlc.fsf@pond.sub.org> (raw)
In-Reply-To: <ec33abcb-409f-4609-9007-3337f3f647ab@linaro.org> ("Philippe Mathieu-Daudé"'s message of "Fri, 9 Aug 2024 10:44:24 +0200")
Philippe Mathieu-Daudé <philmd@linaro.org> writes:
> Hi Markus,
>
> On 8/8/24 20:26, Markus Armbruster wrote:
>> Since we neglect to document several members of ChardevBackendKind,
>> their description in the QEMU QMP Reference manual is "Not
>> documented". Fix that, and improve the existing member documentation.
>>
>> Signed-off-by: Markus Armbruster <armbru@redhat.com>
>> ---
>> qapi/char.json | 44 ++++++++++++++++++++++++++++----------------
>> qapi/pragma.json | 1 -
>> 2 files changed, 28 insertions(+), 17 deletions(-)
>>
>> diff --git a/qapi/char.json b/qapi/char.json
>> index ef58445cee..8a4a87c95c 100644
>> --- a/qapi/char.json
>> +++ b/qapi/char.json
>> @@ -434,37 +434,49 @@
>> ##
>> # @ChardevBackendKind:
>> #
>> -# @pipe: Since 1.5
>> +# @file: regular files
>> #
>> -# @udp: Since 1.5
>> +# @serial: serial host device
>> #
>> -# @mux: Since 1.5
>> +# @parallel: parallel host device
>> #
>> -# @msmouse: Since 1.5
>> +# @pipe: pipes (since 1.5)
>> #
>> -# @wctablet: Since 2.9
>> +# @socket: stream socket
>> #
>> -# @braille: Since 1.5
>> +# @udp: datagram socket (since 1.5)
>> #
>> -# @testdev: Since 2.2
>> +# @pty: pseudo-terminal
>> #
>> -# @stdio: Since 1.5
>> +# @null: provides no input, throws away output
>> #
>> -# @console: Since 1.5
>> +# @mux: (since 1.5)
>> #
>> -# @spicevmc: Since 1.5
>> +# @msmouse: emulated Microsoft serial mouse (since 1.5)
>> #
>> -# @spiceport: Since 1.5
>> +# @wctablet: emulated Wacom Penpartner serial tablet (since 2.9)
>> #
>> -# @qemu-vdagent: Since 6.1
>> +# @braille: Baum Braille device (since 1.5)
>> #
>> -# @dbus: Since 7.0
>> +# @testdev: device for test-suite control (since 2.2)
>> #
>> -# @vc: v1.5
>> +# @stdio: standard I/O (since 1.5)
>> #
>> -# @ringbuf: Since 1.6
>> +# @console: Windows console (since 1.5)
>> #
>> -# @memory: Since 1.5
>> +# @spicevmc: spice vm channel (since 1.5)
>> +#
>> +# @spiceport: Spice port channel (since 1.5)
>> +#
>> +# @qemu-vdagent: Spice vdagent (since 6.1)
>> +#
>> +# @dbus: D-Bus channel (since 7.0)
>> +#
>> +# @vc: virtual console (since v1.5)
>> +#
>> +# @ringbuf: memory ring buffer (since 1.6)
>> +#
>> +# @memory: synonym for @ringbuf (since 1.5)
>
> What is the rule to sort the members?
I like to keep the member descriptions in the same order as their
definitions in 'data'.
As to the order in 'data': sometimes there's a "natural" order or
grouping, and sometimes alphabetical is best. However, we too often add
members without giving order a thought, commonly at the end.
Hope this helps!
next prev parent reply other threads:[~2024-08-09 9:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 18:26 [PATCH 0/6] qapi: Supply some of the missing member documentation Markus Armbruster
2024-08-08 18:26 ` [PATCH 1/6] qapi/char: Supply " Markus Armbruster
2024-08-08 20:48 ` John Snow
2024-08-09 4:51 ` Markus Armbruster
2024-08-09 8:44 ` Philippe Mathieu-Daudé
2024-08-09 9:11 ` Markus Armbruster [this message]
2024-08-12 18:10 ` John Snow
2024-08-08 18:26 ` [PATCH 2/6] qapi/common: " Markus Armbruster
2024-08-09 8:38 ` Philippe Mathieu-Daudé
2024-08-08 18:26 ` [PATCH 3/6] qapi/crypto: " Markus Armbruster
2024-08-09 8:39 ` Philippe Mathieu-Daudé
2024-08-08 18:26 ` [PATCH 4/6] qapi/introspect: " Markus Armbruster
2024-08-09 12:27 ` Eric Blake
2024-08-08 18:26 ` [PATCH 5/6] qapi/pci: " Markus Armbruster
2024-08-09 8:41 ` Philippe Mathieu-Daudé
2024-08-08 18:26 ` [PATCH 6/6] qapi/rocker: " Markus Armbruster
2024-08-09 8:41 ` Philippe Mathieu-Daudé
2024-08-08 20:51 ` [PATCH 0/6] qapi: Supply some of the " John Snow
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=875xsakqlc.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=jiri@resnulli.us \
--cc=jsnow@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--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.