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 <arm...@redhat.com> Message-ID: <20250527073916.1243024-13-arm...@redhat.com> Reviewed-by: Eric Blake <ebl...@redhat.com> --- qapi/block-core.json | 6 +++--- qapi/job.json | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/qapi/block-core.json b/qapi/block-core.json index ad6de151c8..da390f85ac 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 9ddba537db..441cd7772b 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. # -- 2.48.1
