aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMarkus Armbruster <armbru@redhat.com>2025-05-27 09:39:15 +0200
committerMarkus Armbruster <armbru@redhat.com>2025-06-03 08:34:57 +0200
commitfeeb08c260171e8a15236d20f2978c68aae4f569 (patch)
tree17ac68079902227e461d41db49fcad6d0ea8945b
parent901eb8b2d8a14a0378d1c59fe37733366d4da16c (diff)
downloadqemu-feeb08c260171e8a15236d20f2978c68aae4f569.zip
qemu-feeb08c260171e8a15236d20f2978c68aae4f569.tar.gz
qemu-feeb08c260171e8a15236d20f2978c68aae4f569.tar.bz2
qapi: Tidy up references to job state CONCLUDED
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>
-rw-r--r--qapi/block-core.json6
-rw-r--r--qapi/job.json6
2 files changed, 6 insertions, 6 deletions
diff --git a/qapi/block-core.json b/qapi/block-core.json
index ad6de15..da390f8 100644
--- a/qapi/block-core.json
+++ b/qapi/block-core.json
@@ -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.
#
diff --git a/qapi/job.json b/qapi/job.json
index 9ddba53..441cd77 100644
--- a/qapi/job.json
+++ b/qapi/job.json
@@ -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.
#