From: Han Han <hhan@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, lvivier@redhat.com, Han Han <hhan@redhat.com>
Subject: [PATCH] qapi: virtio: Fix the introduced version
Date: Tue, 1 Nov 2022 09:46:47 +0800 [thread overview]
Message-ID: <20221101014647.3000801-1-hhan@redhat.com> (raw)
The items of qapi/virtio.json are introduced at a5ebce38576. They will be
in the version 7.2 not 7.1.
Signed-off-by: Han Han <hhan@redhat.com>
---
qapi/virtio.json | 34 +++++++++++++++++-----------------
1 file changed, 17 insertions(+), 17 deletions(-)
diff --git a/qapi/virtio.json b/qapi/virtio.json
index e47a8fb2e0..872c7e3623 100644
--- a/qapi/virtio.json
+++ b/qapi/virtio.json
@@ -15,7 +15,7 @@
#
# @name: Name of the VirtIODevice
#
-# Since: 7.1
+# Since: 7.2
#
##
{ 'struct': 'VirtioInfo',
@@ -32,7 +32,7 @@
#
# Returns: List of gathered VirtIODevices
#
-# Since: 7.1
+# Since: 7.2
#
# Example:
#
@@ -97,7 +97,7 @@
#
# @log-size: vhost_dev log_size
#
-# Since: 7.1
+# Since: 7.2
#
##
@@ -167,7 +167,7 @@
# Present if the given VirtIODevice has an active vhost
# device.
#
-# Since: 7.1
+# Since: 7.2
#
##
@@ -206,7 +206,7 @@
#
# Returns: VirtioStatus of the virtio device
#
-# Since: 7.1
+# Since: 7.2
#
# Examples:
#
@@ -452,7 +452,7 @@
#
# @unknown-statuses: Virtio device statuses bitmap that have not been decoded
#
-# Since: 7.1
+# Since: 7.2
##
{ 'struct': 'VirtioDeviceStatus',
@@ -471,7 +471,7 @@
# @unknown-protocols: Vhost user device protocol features bitmap that
# have not been decoded
#
-# Since: 7.1
+# Since: 7.2
##
{ 'struct': 'VhostDeviceProtocols',
@@ -492,7 +492,7 @@
# @unknown-dev-features: Virtio device features bitmap that have not
# been decoded
#
-# Since: 7.1
+# Since: 7.2
##
{ 'struct': 'VirtioDeviceFeatures',
@@ -535,7 +535,7 @@
#
# @signalled-used-valid: VirtQueue signalled_used_valid flag
#
-# Since: 7.1
+# Since: 7.2
#
##
@@ -576,7 +576,7 @@
# shadow_avail_idx will not be displayed in the case where
# the selected VirtIODevice has a running vhost device.
#
-# Since: 7.1
+# Since: 7.2
#
# Examples:
#
@@ -666,7 +666,7 @@
#
# @used-size: vhost_virtqueue used_size
#
-# Since: 7.1
+# Since: 7.2
#
##
@@ -699,7 +699,7 @@
#
# Returns: VirtVhostQueueStatus of the vhost_virtqueue
#
-# Since: 7.1
+# Since: 7.2
#
# Examples:
#
@@ -767,7 +767,7 @@
#
# @flags: List of descriptor flags
#
-# Since: 7.1
+# Since: 7.2
#
##
@@ -787,7 +787,7 @@
#
# @ring: VRingAvail ring[] entry at provided index
#
-# Since: 7.1
+# Since: 7.2
#
##
@@ -805,7 +805,7 @@
#
# @idx: VRingUsed index
#
-# Since: 7.1
+# Since: 7.2
#
##
@@ -829,7 +829,7 @@
#
# @used: VRingUsed info
#
-# Since: 7.1
+# Since: 7.2
#
##
@@ -857,7 +857,7 @@
#
# Returns: VirtioQueueElement information
#
-# Since: 7.1
+# Since: 7.2
#
# Examples:
#
--
2.38.1
next reply other threads:[~2022-11-01 1:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 1:46 Han Han [this message]
2022-11-01 10:47 ` [PATCH] qapi: virtio: Fix the introduced version Laurent Vivier
2022-11-02 17:56 ` Laurent Vivier
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=20221101014647.3000801-1-hhan@redhat.com \
--to=hhan@redhat.com \
--cc=lvivier@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).