From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
"Eric Blake" <eblake@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@mailo.com>,
"Igor Mammedov" <imammedo@redhat.com>,
linux-cxl@vger.kernel.org, "Zhao Liu" <zhao1.liu@intel.com>,
"Kevin Wolf" <kwolf@redhat.com>,
"Hanna Reitz" <hreitz@redhat.com>,
"Lukas Straub" <lukasstraub2@web.de>,
"Markus Armbruster" <armbru@redhat.com>,
"Jonathan Cameron" <jic23@kernel.org>,
qemu-block@nongnu.org, "Ani Sinha" <anisinha@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"John Snow" <jsnow@redhat.com>
Subject: [PATCH 02/10] qapi: convert simple data struct intros for misc-arm.json
Date: Thu, 10 Sep 2026 16:38:48 -0400 [thread overview]
Message-ID: <20260910203856.99003-3-jsnow@redhat.com> (raw)
In-Reply-To: <20260910203856.99003-1-jsnow@redhat.com>
Signed-off-by: John Snow <jsnow@redhat.com>
---
qapi/misc-arm.json | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/qapi/misc-arm.json b/qapi/misc-arm.json
index a7b5498d2d3..8cb2ea77951 100644
--- a/qapi/misc-arm.json
+++ b/qapi/misc-arm.json
@@ -5,11 +5,10 @@
##
# @GICCapability:
-#
-# The struct describes capability for a specific GIC (Generic
-# Interrupt Controller) version. These bits are not only decided by
-# QEMU/KVM software version, but also decided by the hardware that the
-# program is running upon.
+# The struct describes capability for a specific GIC (Generic
+# Interrupt Controller) version. These bits are not only decided
+# by QEMU/KVM software version, but also decided by the hardware
+# that the program is running upon.
#
# @version: version of GIC to be described. Currently, only 2 and 3
# are supported.
--
2.55.0
next prev parent reply other threads:[~2026-09-10 20:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 20:38 [PATCH 00/10] qapi: convert simple data struct/alternate intro sections John Snow
2026-09-10 20:38 ` [PATCH 01/10] qapi: convert simple data struct intros for uefi.json John Snow
2026-09-10 20:38 ` John Snow [this message]
2026-09-10 20:38 ` [PATCH 03/10] qapi: convert simple data struct intros for acpi.json John Snow
2026-09-11 9:01 ` Markus Armbruster
2026-09-10 20:38 ` [PATCH 04/10] qapi: convert simple data struct intros for run-state.json John Snow
2026-09-10 20:38 ` [PATCH 05/10] qapi: convert simple data struct intros for yank.json John Snow
2026-09-10 20:38 ` [PATCH 06/10] qapi: convert simple data struct intros for cxl.json John Snow
2026-09-10 20:38 ` [PATCH 07/10] qapi: convert simple data struct intros for virtio.json John Snow
2026-09-10 20:38 ` [PATCH 08/10] qapi: convert simple data struct intros for machine.json John Snow
2026-09-11 8:59 ` Markus Armbruster
2026-09-10 20:38 ` [PATCH 09/10] qapi: convert simple data struct intros for block-core.json John Snow
2026-09-10 20:38 ` [PATCH 10/10] qapi: convert simple alternate intros for common.json John Snow
2026-09-11 9:02 ` [PATCH 00/10] qapi: convert simple data struct/alternate intro sections 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=20260910203856.99003-3-jsnow@redhat.com \
--to=jsnow@redhat.com \
--cc=anisinha@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=hreitz@redhat.com \
--cc=imammedo@redhat.com \
--cc=jic23@kernel.org \
--cc=kwolf@redhat.com \
--cc=linux-cxl@vger.kernel.org \
--cc=lukasstraub2@web.de \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@mailo.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=zhao1.liu@intel.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