From: Luiz Capitulino <lcapitulino@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qapi-schema: Use existing type for drive-backup arguments
Date: Tue, 9 Jul 2013 09:31:38 -0400 [thread overview]
Message-ID: <20130709093138.5c319b47@redhat.com> (raw)
In-Reply-To: <1373357135-9294-1-git-send-email-kwolf@redhat.com>
On Tue, 9 Jul 2013 10:05:35 +0200
Kevin Wolf <kwolf@redhat.com> wrote:
> This removes duplicated definitions and documentation by reusing the
> existing data type.
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Applied to the qmp branch, thanks.
> ---
>
> To be applied on top of '[PATCH v3 0/3] qapi: Top-level type reference for
> command definitions'
>
> qapi-schema.json | 32 ++------------------------------
> 1 file changed, 2 insertions(+), 30 deletions(-)
>
> diff --git a/qapi-schema.json b/qapi-schema.json
> index a90aeb1..b251d28 100644
> --- a/qapi-schema.json
> +++ b/qapi-schema.json
> @@ -1791,42 +1791,14 @@
> # The operation can be stopped before it has completed using the
> # block-job-cancel command.
> #
> -# @device: the name of the device which should be copied.
> -#
> -# @target: the target of the new image. If the file exists, or if it
> -# is a device, the existing file/device will be used as the new
> -# destination. If it does not exist, a new file will be created.
> -#
> -# @format: #optional the format of the new destination, default is to
> -# probe if @mode is 'existing', else the format of the source
> -#
> -# @mode: #optional whether and how QEMU should create a new image, default is
> -# 'absolute-paths'.
> -#
> -# @speed: #optional the maximum speed, in bytes per second
> -#
> -# @on-source-error: #optional the action to take on an error on the source,
> -# default 'report'. 'stop' and 'enospc' can only be used
> -# if the block device supports io-status (see BlockInfo).
> -#
> -# @on-target-error: #optional the action to take on an error on the target,
> -# default 'report' (no limitations, since this applies to
> -# a different block device than @device).
> -#
> -# Note that @on-source-error and @on-target-error only affect background I/O.
> -# If an error occurs during a guest write request, the device's rerror/werror
> -# actions will be used.
> +# For the arguments, see the documentation of DriveBackup.
> #
> # Returns: nothing on success
> # If @device is not a valid block device, DeviceNotFound
> #
> # Since 1.6
> ##
> -{ 'command': 'drive-backup',
> - 'data': { 'device': 'str', 'target': 'str', '*format': 'str',
> - '*mode': 'NewImageMode', '*speed': 'int',
> - '*on-source-error': 'BlockdevOnError',
> - '*on-target-error': 'BlockdevOnError' } }
> +{ 'command': 'drive-backup', 'data': 'DriveBackup' }
>
> ##
> # @drive-mirror
prev parent reply other threads:[~2013-07-09 13:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 8:05 [Qemu-devel] [PATCH] qapi-schema: Use existing type for drive-backup arguments Kevin Wolf
2013-07-09 11:47 ` Eric Blake
2013-07-09 11:58 ` Fam Zheng
2013-07-09 12:04 ` Kevin Wolf
2013-07-09 12:09 ` Eric Blake
2013-07-09 12:17 ` Kevin Wolf
2013-07-09 12:07 ` Eric Blake
2013-07-09 12:45 ` Fam Zheng
2013-07-09 13:31 ` Luiz Capitulino [this message]
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=20130709093138.5c319b47@redhat.com \
--to=lcapitulino@redhat.com \
--cc=kwolf@redhat.com \
--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).