From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: richard.henderson@linaro.org,
Elena Ufimtseva <elena.ufimtseva@oracle.com>,
John G Johnson <john.g.johnson@oracle.com>,
Jagannathan Raman <jag.raman@oracle.com>,
qemu-stable@nongnu.org, John Snow <jsnow@redhat.com>
Subject: [PULL 01/14] qapi/qom: Document feature unstable of @x-vfio-user-server
Date: Wed, 17 Jul 2024 12:48:54 +0200 [thread overview]
Message-ID: <20240717104907.2962784-2-armbru@redhat.com> (raw)
In-Reply-To: <20240717104907.2962784-1-armbru@redhat.com>
Commit 8f9a9259d32c added ObjectType member @x-vfio-user-server with
feature unstable, but neglected to explain why it is unstable. Do
that now.
Fixes: 8f9a9259d32c (vfio-user: define vfio-user-server object)
Cc: Elena Ufimtseva <elena.ufimtseva@oracle.com>
Cc: John G Johnson <john.g.johnson@oracle.com>
Cc: Jagannathan Raman <jag.raman@oracle.com>
Cc: qemu-stable@nongnu.org
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-ID: <20240703095310.1242102-1-armbru@redhat.com>
Reviewed-by: John Snow <jsnow@redhat.com>
[Indentation fixed]
---
qapi/qom.json | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/qapi/qom.json b/qapi/qom.json
index 8e75a419c3..3e52aec8fb 100644
--- a/qapi/qom.json
+++ b/qapi/qom.json
@@ -1024,7 +1024,8 @@
#
# Features:
#
-# @unstable: Member @x-remote-object is experimental.
+# @unstable: Members @x-remote-object and @x-vfio-user-server are
+# experimental.
#
# Since: 6.0
##
--
2.45.0
next prev parent reply other threads:[~2024-07-17 10:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 10:48 [PULL 00/14] QAPI patches patches for 2024-07-17 Markus Armbruster
2024-07-17 10:48 ` Markus Armbruster [this message]
2024-07-17 10:48 ` [PULL 02/14] qapi/pci: Clean up documentation around PciDeviceClass Markus Armbruster
2024-07-17 10:48 ` [PULL 03/14] qapi/machine: Clean up documentation around CpuInstanceProperties Markus Armbruster
2024-07-17 10:48 ` [PULL 04/14] qapi/machine: Clarify query-uuid value when none has been specified Markus Armbruster
2024-07-17 10:48 ` [PULL 05/14] qapi/sockets: Move deprecation note out of SocketAddress doc comment Markus Armbruster
2024-07-17 10:48 ` [PULL 06/14] qapi/ui: Drop note on naming of SpiceQueryMouseMode Markus Armbruster
2024-07-17 10:49 ` [PULL 07/14] docs/qapidoc: factor out do_parse() Markus Armbruster
2024-07-17 10:49 ` [PULL 08/14] docs/qapidoc: create qmp-example directive Markus Armbruster
2024-07-17 10:49 ` [PULL 09/14] docs/qapidoc: add QMP highlighting to annotated qmp-example blocks Markus Armbruster
2024-07-17 10:49 ` [PULL 10/14] docs/sphinx: add CSS styling for qmp-example directive Markus Armbruster
2024-07-17 10:49 ` [PULL 11/14] qapi: convert "Example" sections without titles Markus Armbruster
2024-07-17 10:49 ` [PULL 12/14] qapi: convert "Example" sections with titles Markus Armbruster
2024-07-17 10:49 ` [PULL 13/14] qapi: convert "Example" sections with longer prose Markus Armbruster
2024-07-17 10:49 ` [PULL 14/14] qapi: remove "Example" doc section Markus Armbruster
2024-07-18 11:22 ` [PULL 00/14] QAPI patches patches for 2024-07-17 Richard Henderson
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=20240717104907.2962784-2-armbru@redhat.com \
--to=armbru@redhat.com \
--cc=elena.ufimtseva@oracle.com \
--cc=jag.raman@oracle.com \
--cc=john.g.johnson@oracle.com \
--cc=jsnow@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=richard.henderson@linaro.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).