From: Alberto Garcia <berto@igalia.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Alberto Garcia <berto@igalia.com>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: [Qemu-devel] [PATCH v2 0/2] Allow x-blockdev-del on a BB with a monitor-owned BDS
Date: Tue, 9 Feb 2016 17:57:34 +0200 [thread overview]
Message-ID: <cover.1455033112.git.berto@igalia.com> (raw)
This series allow x-blockdev-del to be peformed on a BlockBackend that
has a BDS inserted with an additional reference if that reference is
from the monitor.
v2 squashes two of the patches together and fixes the commit message,
but is otherwise the same as v1.
Regards,
Berto
v2:
- Squash patch 2 (with the tests) into the first one with the code [Eric]
- s/splitted/split/ in the description of the tests [Eric]
v1: https://lists.gnu.org/archive/html/qemu-block/2016-02/msg00247.html
- Initial version
Alberto Garcia (2):
block: Allow x-blockdev-del on a BB with a monitor-owned BDS
block: Update the x-blockdev-del documentation
blockdev.c | 13 ++++++++++---
qapi/block-core.json | 5 ++++-
qmp-commands.hx | 5 ++++-
tests/qemu-iotests/139 | 30 +++++++++++++++++++++++++-----
tests/qemu-iotests/139.out | 4 ++--
5 files changed, 45 insertions(+), 12 deletions(-)
--
2.7.0
next reply other threads:[~2016-02-09 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 15:57 Alberto Garcia [this message]
2016-02-09 15:57 ` [Qemu-devel] [PATCH v2 1/2] block: Allow x-blockdev-del on a BB with a monitor-owned BDS Alberto Garcia
2016-02-24 16:15 ` Max Reitz
2016-02-25 11:11 ` Alberto Garcia
2016-02-26 8:58 ` Kevin Wolf
2016-02-26 9:09 ` Alberto Garcia
2016-02-09 15:57 ` [Qemu-devel] [PATCH v2 2/2] block: Update the x-blockdev-del documentation Alberto Garcia
2016-02-24 12:51 ` [Qemu-devel] [PATCH v2 0/2] Allow x-blockdev-del on a BB with a monitor-owned BDS Alberto Garcia
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=cover.1455033112.git.berto@igalia.com \
--to=berto@igalia.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).