From: Jeff Cody <jcody@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
Kevin Wolf <kwolf@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Eric Blake <eblake@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v5 15/16] block/backup: qapi documentation fixup
Date: Thu, 6 Sep 2018 13:03:08 -0400 [thread overview]
Message-ID: <20180906170308.GM22117@localhost.localdomain> (raw)
In-Reply-To: <20180906130225.5118-16-jsnow@redhat.com>
On Thu, Sep 06, 2018 at 09:02:24AM -0400, John Snow wrote:
> Fix documentation to match the other jobs amended for 3.1.
>
> Signed-off-by: John Snow <jsnow@redhat.com>
> Reviewed-by: Max Reitz <mreitz@redhat.com>
Reviewed-by: Jeff Cody <jcody@redhat.com>
> ---
> qapi/block-core.json | 18 ++++++++++--------
> 1 file changed, 10 insertions(+), 8 deletions(-)
>
> diff --git a/qapi/block-core.json b/qapi/block-core.json
> index f877e9e414..c0b3d33dbb 100644
> --- a/qapi/block-core.json
> +++ b/qapi/block-core.json
> @@ -1272,13 +1272,14 @@
> # a different block device than @device).
> #
> # @auto-finalize: When false, this job will wait in a PENDING state after it has
> -# finished its work, waiting for @block-job-finalize.
> -# When true, this job will automatically perform its abort or
> -# commit actions.
> +# finished its work, waiting for @block-job-finalize before
> +# making any block graph changes.
> +# When true, this job will automatically
> +# perform its abort or commit actions.
> # Defaults to true. (Since 2.12)
> #
> # @auto-dismiss: When false, this job will wait in a CONCLUDED state after it
> -# has completed ceased all work, and wait for @block-job-dismiss.
> +# has completely ceased all work, and awaits @block-job-dismiss.
> # When true, this job will automatically disappear from the query
> # list without user intervention.
> # Defaults to true. (Since 2.12)
> @@ -1327,13 +1328,14 @@
> # a different block device than @device).
> #
> # @auto-finalize: When false, this job will wait in a PENDING state after it has
> -# finished its work, waiting for @block-job-finalize.
> -# When true, this job will automatically perform its abort or
> -# commit actions.
> +# finished its work, waiting for @block-job-finalize before
> +# making any block graph changes.
> +# When true, this job will automatically
> +# perform its abort or commit actions.
> # Defaults to true. (Since 2.12)
> #
> # @auto-dismiss: When false, this job will wait in a CONCLUDED state after it
> -# has completed ceased all work, and wait for @block-job-dismiss.
> +# has completely ceased all work, and awaits @block-job-dismiss.
> # When true, this job will automatically disappear from the query
> # list without user intervention.
> # Defaults to true. (Since 2.12)
> --
> 2.14.4
>
next prev parent reply other threads:[~2018-09-06 17:03 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 13:02 [Qemu-devel] [PATCH v5 00/16] jobs: Job Exit Refactoring Pt 2 John Snow
2018-09-06 13:02 ` [Qemu-devel] [PATCH v5 01/16] block/commit: add block job creation flags John Snow
2018-09-06 13:02 ` [Qemu-devel] [PATCH v5 02/16] block/mirror: " John Snow
2018-09-06 13:02 ` [Qemu-devel] [PATCH v5 03/16] block/stream: " John Snow
2018-09-06 13:02 ` [Qemu-devel] [PATCH v5 04/16] block/commit: refactor commit to use job callbacks John Snow
2018-09-06 16:19 ` Jeff Cody
2018-09-07 23:14 ` Max Reitz
2018-09-06 13:02 ` [Qemu-devel] [PATCH v5 05/16] block/mirror: don't install backing chain on abort John Snow
2018-09-06 16:21 ` Jeff Cody
2018-09-07 23:15 ` Max Reitz
2018-09-06 13:02 ` [Qemu-devel] [PATCH v5 06/16] block/mirror: conservative mirror_exit refactor John Snow
2018-09-06 16:57 ` Jeff Cody
2018-09-06 20:31 ` John Snow
2018-09-07 23:16 ` Max Reitz
2018-09-06 13:02 ` [Qemu-devel] [PATCH v5 07/16] block/stream: refactor stream to use job callbacks John Snow
2018-09-06 16:58 ` Jeff Cody
2018-09-06 13:02 ` [Qemu-devel] [PATCH v5 08/16] tests/blockjob: replace Blockjob with Job John Snow
2018-09-06 16:58 ` Jeff Cody
2018-09-06 13:02 ` [Qemu-devel] [PATCH v5 09/16] tests/test-blockjob: remove exit callback John Snow
2018-09-06 16:58 ` Jeff Cody
2018-09-06 13:02 ` [Qemu-devel] [PATCH v5 10/16] tests/test-blockjob-txn: move .exit to .clean John Snow
2018-09-06 16:58 ` Jeff Cody
2018-09-06 13:02 ` [Qemu-devel] [PATCH v5 11/16] jobs: remove .exit callback John Snow
2018-09-06 16:59 ` Jeff Cody
2018-09-06 13:02 ` [Qemu-devel] [PATCH v5 12/16] qapi/block-commit: expose new job properties John Snow
2018-09-06 17:01 ` Jeff Cody
2018-09-06 13:02 ` [Qemu-devel] [PATCH v5 13/16] qapi/block-mirror: " John Snow
2018-09-06 17:01 ` Jeff Cody
2018-09-06 13:02 ` [Qemu-devel] [PATCH v5 14/16] qapi/block-stream: " John Snow
2018-09-06 17:02 ` Jeff Cody
2018-09-06 13:02 ` [Qemu-devel] [PATCH v5 15/16] block/backup: qapi documentation fixup John Snow
2018-09-06 17:03 ` Jeff Cody [this message]
2018-09-06 13:02 ` [Qemu-devel] [PATCH v5 16/16] blockdev: document transactional shortcomings John Snow
2018-09-06 17:03 ` Jeff Cody
2018-09-07 23:23 ` Max Reitz
2018-09-07 23:29 ` [Qemu-devel] [PATCH v5 00/16] jobs: Job Exit Refactoring Pt 2 Max Reitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180906170308.GM22117@localhost.localdomain \
--to=jcody@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).