From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: jsnow@redhat.com, eblake@redhat.com, vsementsov@yandex-team.ru,
thuth@redhat.com, berrange@redhat.com, kchamart@redhat.com,
mst@redhat.com, sgarzare@redhat.com
Subject: Re: [PATCH 3/8] qapi: Clean up whitespace between definitions
Date: Fri, 31 Oct 2025 11:02:29 +0100 [thread overview]
Message-ID: <3bd0c9b1-e35d-4663-a611-d25d8c307999@linaro.org> (raw)
In-Reply-To: <20251031094751.2817932-4-armbru@redhat.com>
On 31/10/25 10:47, Markus Armbruster wrote:
> Consistently separate definitions with a single blank line.
> Consistently separate member descriptions with a blank line.
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> qapi/acpi-hest.json | 1 -
> qapi/char.json | 1 -
> qapi/crypto.json | 1 +
> qapi/cxl.json | 1 -
> qapi/migration.json | 3 +++
> qapi/misc-i386.json | 2 --
> qapi/net.json | 3 ---
> qapi/qom.json | 3 ---
> qapi/run-state.json | 1 -
> qapi/ui.json | 2 +-
> qapi/virtio.json | 2 --
> 11 files changed, 5 insertions(+), 15 deletions(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2025-10-31 10:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 9:47 [PATCH 0/8] A QAPI schema doc markup fix, and style cleanup Markus Armbruster
2025-10-31 9:47 ` [PATCH 1/8] qapi/audio: Fix description markup of AudiodevDBusOptions @nsamples Markus Armbruster
2025-10-31 9:53 ` Vladimir Sementsov-Ogievskiy
2025-10-31 11:46 ` Markus Armbruster
2025-10-31 10:02 ` Philippe Mathieu-Daudé
2025-10-31 9:47 ` [PATCH 2/8] qapi: Refill doc comments to conform to conventions Markus Armbruster
2025-10-31 10:25 ` Vladimir Sementsov-Ogievskiy
2025-10-31 11:47 ` Markus Armbruster
2025-10-31 9:47 ` [PATCH 3/8] qapi: Clean up whitespace between definitions Markus Armbruster
2025-10-31 10:02 ` Philippe Mathieu-Daudé [this message]
2025-10-31 10:26 ` Vladimir Sementsov-Ogievskiy
2025-10-31 9:47 ` [PATCH 4/8] qga/qapi-schema: Refill doc comments to conform to conventions Markus Armbruster
2025-10-31 10:28 ` Vladimir Sementsov-Ogievskiy
2025-10-31 9:47 ` [PATCH 5/8] qga/qapi-schema: Clean up whitespace between definitions Markus Armbruster
2025-10-31 10:02 ` Philippe Mathieu-Daudé
2025-10-31 10:28 ` Vladimir Sementsov-Ogievskiy
2025-10-31 9:47 ` [PATCH 6/8] docs/interop: Refill QAPI doc comments to conform to conventions Markus Armbruster
2025-10-31 10:32 ` Vladimir Sementsov-Ogievskiy
2025-10-31 11:41 ` Markus Armbruster
2025-10-31 9:47 ` [PATCH 7/8] docs/interop/firmware: Literal block markup Markus Armbruster
2025-10-31 10:03 ` Philippe Mathieu-Daudé
2025-10-31 10:36 ` Vladimir Sementsov-Ogievskiy
2025-10-31 9:47 ` [PATCH 8/8] docs/interop: Add test to keep vhost-user.json sane Markus Armbruster
2025-10-31 10:53 ` Vladimir Sementsov-Ogievskiy
2025-10-31 11:45 ` 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=3bd0c9b1-e35d-4663-a611-d25d8c307999@linaro.org \
--to=philmd@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=jsnow@redhat.com \
--cc=kchamart@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=thuth@redhat.com \
--cc=vsementsov@yandex-team.ru \
/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).