From: Max Reitz <mreitz@redhat.com>
To: Alberto Garcia <berto@igalia.com>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
Eric Blake <eblake@redhat.com>, Jeff Cody <jcody@redhat.com>,
John Snow <jsnow@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 08/11] stream: Add 'job-id' parameter to 'block-stream'
Date: Tue, 5 Jul 2016 17:45:26 +0200 [thread overview]
Message-ID: <c62da451-6ffc-b617-b25d-61475fed12f0@redhat.com> (raw)
In-Reply-To: <ada2feab918659449dc92717963ef062c1c527fa.1467727577.git.berto@igalia.com>
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
On 05.07.2016 16:28, Alberto Garcia wrote:
> This patch adds a new optional 'job-id' parameter to 'block-stream',
> allowing the user to specify the ID of the block job to be created.
>
> The HMP 'block_stream' command remains unchanged.
>
> Signed-off-by: Alberto Garcia <berto@igalia.com>
> Reviewed-by: Kevin Wolf <kwolf@redhat.com>
> ---
> block/stream.c | 12 ++++++------
> blockdev.c | 6 +++---
> hmp.c | 2 +-
> include/block/block_int.h | 10 ++++++----
> qapi/block-core.json | 8 ++++++--
> qmp-commands.hx | 4 +++-
> 6 files changed, 25 insertions(+), 17 deletions(-)
Reviewed-by: Max Reitz <mreitz@redhat.com>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 498 bytes --]
next prev parent reply other threads:[~2016-07-05 15:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 14:28 [Qemu-devel] [PATCH v4 00/11] Allow creating block jobs with a user-defined ID Alberto Garcia
2016-07-05 14:28 ` [Qemu-devel] [PATCH v4 01/11] stream: Fix prototype of stream_start() Alberto Garcia
2016-07-05 14:28 ` [Qemu-devel] [PATCH v4 02/11] blockjob: Update description of the 'id' field Alberto Garcia
2016-07-05 14:28 ` [Qemu-devel] [PATCH v4 03/11] blockjob: Add block_job_get() Alberto Garcia
2016-07-05 14:28 ` [Qemu-devel] [PATCH v4 04/11] block: Use block_job_get() in find_block_job() Alberto Garcia
2016-07-05 14:28 ` [Qemu-devel] [PATCH v4 05/11] blockjob: Add 'job_id' parameter to block_job_create() Alberto Garcia
2016-07-05 14:28 ` [Qemu-devel] [PATCH v4 06/11] mirror: Add 'job-id' parameter to 'blockdev-mirror' and 'drive-mirror' Alberto Garcia
2016-07-05 15:41 ` Max Reitz
2016-07-05 14:28 ` [Qemu-devel] [PATCH v4 07/11] backup: Add 'job-id' parameter to 'blockdev-backup' and 'drive-backup' Alberto Garcia
2016-07-05 15:44 ` Max Reitz
2016-07-05 14:28 ` [Qemu-devel] [PATCH v4 08/11] stream: Add 'job-id' parameter to 'block-stream' Alberto Garcia
2016-07-05 15:45 ` Max Reitz [this message]
2016-07-05 14:29 ` [Qemu-devel] [PATCH v4 09/11] commit: Add 'job-id' parameter to 'block-commit' Alberto Garcia
2016-07-05 15:46 ` Max Reitz
2016-07-05 14:29 ` [Qemu-devel] [PATCH v4 10/11] qemu-img: Set the ID of the block job in img_commit() Alberto Garcia
2016-07-05 15:56 ` Max Reitz
2016-07-06 12:07 ` Alberto Garcia
2016-07-05 14:29 ` [Qemu-devel] [PATCH v4 11/11] blockjob: Update description of the 'device' field in the QMP API Alberto Garcia
2016-07-07 12:48 ` [Qemu-devel] [PATCH v4 00/11] Allow creating block jobs with a user-defined ID Kevin Wolf
2016-07-07 15:12 ` Alberto Garcia
2016-07-07 15:34 ` John Snow
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=c62da451-6ffc-b617-b25d-61475fed12f0@redhat.com \
--to=mreitz@redhat.com \
--cc=berto@igalia.com \
--cc=eblake@redhat.com \
--cc=jcody@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@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).