motorhead/qemu
1
0
Fork 0
mirror of https://github.com/Motorhead1991/qemu.git synced 2025-09-09 00:07:57 -06:00
Code Issues Projects Releases Packages Wiki Activity Actions

qapi: Mention both job-cancel and block-job-cancel in doc comments

Browse source 
Several doc comments mention block-job-cancel where the more generic
job-cancel would also work.  Adjust them to mention both.

Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-ID: <20250527073916.1243024-12-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
This commit is contained in:
Markus Armbruster 2025-05-27 09:39:14 +02:00
parent 5ca6400cad
commit 901eb8b2d8
1 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
qapi/block-core.json
View file

@ -1894,7 +1894,7 @@
# The status of ongoing drive-backup operations can be checked with
# query-block-jobs where the BlockJobInfo.type field has the value
# 'backup'. The operation can be stopped before it has completed
# using the block-job-cancel command.
# using the job-cancel or block-job-cancel command.
#
# Features:
#
@ -1925,7 +1925,7 @@
# The status of ongoing blockdev-backup operations can be checked with
# query-block-jobs where the BlockJobInfo.type field has the value
# 'backup'. The operation can be stopped before it has completed
# using the block-job-cancel command.
# using the job-cancel or block-job-cancel command.
#
# Errors:
# - If @device is not a valid block device, DeviceNotFound
@ -2788,7 +2788,7 @@
# immediately once streaming has started. The status of ongoing block
# streaming operations can be checked with query-block-jobs. The
# operation can be stopped before it has completed using the
# block-job-cancel command.
# job-cancel or block-job-cancel command.
#
# The node that receives the data is called the top image, can be
# located in any part of the chain (but always above the base image;
@ -3075,8 +3075,8 @@
#
# This command will refuse to operate on any job that has not yet
# reached its terminal state, JOB_STATUS_CONCLUDED. For jobs that
# make use of the BLOCK_JOB_READY event, block-job-cancel or
# job-complete will still need to be used as appropriate.
# make use of the BLOCK_JOB_READY event, job-cancel, block-job-cancel
# or job-complete will still need to be used as appropriate.
#
# @id: The job identifier.
#