diff options
| author | Max Reitz <mreitz@redhat.com> | 2017-11-10 23:43:02 +0100 |
|---|---|---|
| committer | Max Reitz <mreitz@redhat.com> | 2018-01-23 12:34:42 +0100 |
| commit | 34ce1111416986e62fbb6d55e0a7d45bbb9802ce (patch) | |
| tree | 05589396f52601fc34e9ea5feb408ad37b0af894 /blockdev.c | |
| parent | 82fcf66e052d6dae834255a814969c67e13b6791 (diff) | |
| download | qemu-34ce1111416986e62fbb6d55e0a7d45bbb9802ce.tar.gz | |
blockdev: Mark BD-{remove,insert}-medium stable
Now that iotest 093 test proves that the throttling configuration
survives a blockdev-remove-medium/blockdev-insert-medium pair, the
original reason for declaring these commands experimental is gone
(see commit 6e0abc251dd4f8eba1f53656dfede12e5840e83b).
Signed-off-by: Max Reitz <mreitz@redhat.com>
Message-id: 20171110224302.14424-5-mreitz@redhat.com
Reviewed-by: Alberto Garcia <berto@igalia.com>
Signed-off-by: Max Reitz <mreitz@redhat.com>
Diffstat (limited to 'blockdev.c')
| -rw-r--r-- | blockdev.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/blockdev.c b/blockdev.c index 2f9aef4167..8e977eef11 100644 --- a/blockdev.c +++ b/blockdev.c @@ -2508,7 +2508,7 @@ out: aio_context_release(aio_context); } -void qmp_x_blockdev_remove_medium(const char *id, Error **errp) +void qmp_blockdev_remove_medium(const char *id, Error **errp) { blockdev_remove_medium(false, NULL, true, id, errp); } @@ -2586,8 +2586,8 @@ static void blockdev_insert_medium(bool has_device, const char *device, qmp_blockdev_insert_anon_medium(blk, bs, errp); } -void qmp_x_blockdev_insert_medium(const char *id, const char *node_name, - Error **errp) +void qmp_blockdev_insert_medium(const char *id, const char *node_name, + Error **errp) { blockdev_insert_medium(false, NULL, true, id, node_name, errp); } |