diff options
| author | Markus Armbruster <armbru@redhat.com> | 2023-07-20 09:16:09 +0200 |
|---|---|---|
| committer | Markus Armbruster <armbru@redhat.com> | 2023-07-26 14:51:36 +0200 |
| commit | 9e272073e1c41acb3ba1e43b69c7a3f9c26089c2 (patch) | |
| tree | 177761a148e7ea59ce43bce26910b27c69216878 /qapi/migration.json | |
| parent | e27a9d628d7a9d0c31bc48c82937dd73dbbca01a (diff) | |
| download | qemu-9e272073e1c41acb3ba1e43b69c7a3f9c26089c2.zip qemu-9e272073e1c41acb3ba1e43b69c7a3f9c26089c2.tar.gz qemu-9e272073e1c41acb3ba1e43b69c7a3f9c26089c2.tar.bz2 | |
qapi: Reformat recent doc comments to conform to current conventions
Since commit a937b6aa739 (qapi: Reformat doc comments to conform to
current conventions), a number of comments not conforming to the
current formatting conventions were added. No problem, just sweep
the entire documentation once more.
To check the generated documentation does not change, I compared the
generated HTML before and after this commit with "wdiff -3". Finds no
differences. Comparing with diff is not useful, as the reflown
paragraphs are visible there.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-ID: <20230720071610.1096458-7-armbru@redhat.com>
Diffstat (limited to 'qapi/migration.json')
| -rw-r--r-- | qapi/migration.json | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/qapi/migration.json b/qapi/migration.json index 2a6565a..476b90b 100644 --- a/qapi/migration.json +++ b/qapi/migration.json @@ -465,8 +465,8 @@ # block devices (and thus take locks) immediately at the end of # migration. (since 3.0) # -# @x-ignore-shared: If enabled, QEMU will not migrate shared memory that is -# accessible on the destination machine. (since 4.0) +# @x-ignore-shared: If enabled, QEMU will not migrate shared memory +# that is accessible on the destination machine. (since 4.0) # # @validate-uuid: Send the UUID of the source to allow the destination # to ensure it is the same. (since 4.2) @@ -490,9 +490,9 @@ # @switchover-ack: If enabled, migration will not stop the source VM # and complete the migration until an ACK is received from the # destination that it's OK to do so. Exactly when this ACK is -# sent depends on the migrated devices that use this feature. -# For example, a device can use it to make sure some of its data -# is sent and loaded in the destination before doing switchover. +# sent depends on the migrated devices that use this feature. For +# example, a device can use it to make sure some of its data is +# sent and loaded in the destination before doing switchover. # This can reduce downtime if devices that support this capability # are present. 'return-path' capability must be enabled to use # it. (since 8.1) |