friedkiwi/qemu
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

qapi: Tidy up references to job state CONCLUDED

Browse Source 
When talking about the job state machine, we refer to the states like
READY, ABORTING, CONCLUDED, and so forth.  Except in two places, where
we use JOB_STATUS_CONCLUDED.  Replace by CONCLUDED for consistency.

We should arguably use the JobStatus enum values instead.  Left for
another day.

Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-ID: <20250527073916.1243024-13-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
This commit is contained in:
Markus Armbruster
2025-05-27 09:39:15 +02:00
parent 901eb8b2d8
commit feeb08c260
2 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
qapi/block-core.json
View File

@@ -3074,9 +3074,9 @@
# jobs.
#
# 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, job-cancel, block-job-cancel
# or job-complete will still need to be used as appropriate.
# reached its terminal state, CONCLUDED. For jobs that 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.
#

6
qapi/job.json
View File

@@ -223,9 +223,9 @@
# jobs.
#
# 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 JOB_READY event, job-cancel or job-complete will still
# need to be used as appropriate.
# reached its terminal state, CONCLUDED. For jobs that make use of
# the JOB_READY event, job-cancel or job-complete will still need to
# be used as appropriate.
#
# @id: The job identifier.
#