From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: [Qemu-devel] [PATCH v9 00/15] blockdev: BlockBackend and media
Date: Fri, 6 Nov 2015 16:27:05 +0100 [thread overview]
Message-ID: <1446823626-12525-1-git-send-email-mreitz@redhat.com> (raw)
Patch 11 of the last series broke the OS X build due to ui/cocoa.m
directly referencing qmp_change_blockdev() (which was an internal
function not directly mapped to any QMP command before, now it becomes
an "external" function and is renamed qmp_blockdev_change_medium()).
This v9 consists only of that patch, because the rest is completely
unchanged from v8.
Unfortunately, neither am I rich enough nor do I have the immediate
intention of buying Apple hardware any time soon anyway, so I have no
way of verifying that this changed version builds on OS X. I would
appreciate help with that.
Oh, and if anybody ever asks me again why it might be a bad idea to put
management code into the GUI layer of one specific operating system...
git-backport-diff against v8:
Key:
[----] : patches are identical
[####] : number of functional differences between upstream/downstream patch
[down] : patch is downstream-only
The flags [FC] indicate (F)unctional and (C)ontextual differences, respectively
001/15:[----] [--] 'block: Add blk_remove_bs()'
002/15:[----] [--] 'block: Make bdrv_states public'
003/15:[----] [--] 'block: Add functions for inheriting a BBRS'
004/15:[----] [--] 'blockdev: Add blockdev-open-tray'
005/15:[----] [--] 'blockdev: Add blockdev-close-tray'
006/15:[----] [--] 'blockdev: Add blockdev-remove-medium'
007/15:[----] [--] 'blockdev: Add blockdev-insert-medium'
008/15:[----] [--] 'blockdev: Implement eject with basic operations'
009/15:[----] [--] 'blockdev: Implement change with basic operations'
010/15:[----] [--] 'block: Inquire tray state before tray-moved events'
011/15:[0010] [FC] 'qmp: Introduce blockdev-change-medium'
012/15:[----] [--] 'hmp: Use blockdev-change-medium for change command'
013/15:[----] [--] 'blockdev: read-only-mode for blockdev-change-medium'
014/15:[----] [--] 'hmp: Add read-only-mode option to change command'
015/15:[----] [--] 'iotests: Add test for change-related QMP commands'
Max Reitz (15):
block: Add blk_remove_bs()
block: Make bdrv_states public
block: Add functions for inheriting a BBRS
blockdev: Add blockdev-open-tray
blockdev: Add blockdev-close-tray
blockdev: Add blockdev-remove-medium
blockdev: Add blockdev-insert-medium
blockdev: Implement eject with basic operations
blockdev: Implement change with basic operations
block: Inquire tray state before tray-moved events
qmp: Introduce blockdev-change-medium
hmp: Use blockdev-change-medium for change command
blockdev: read-only-mode for blockdev-change-medium
hmp: Add read-only-mode option to change command
iotests: Add test for change-related QMP commands
block.c | 3 +-
block/block-backend.c | 56 +++-
blockdev.c | 286 ++++++++++++----
hmp-commands.hx | 20 +-
hmp.c | 47 ++-
include/block/block_int.h | 2 +
include/sysemu/block-backend.h | 3 +
include/sysemu/blockdev.h | 2 -
qapi-schema.json | 6 +-
qapi/block-core.json | 126 ++++++++
qmp-commands.hx | 218 +++++++++++++
qmp.c | 3 +-
tests/qemu-iotests/118 | 720 +++++++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/118.out | 5 +
tests/qemu-iotests/group | 1 +
ui/cocoa.m | 10 +-
16 files changed, 1402 insertions(+), 106 deletions(-)
create mode 100755 tests/qemu-iotests/118
create mode 100644 tests/qemu-iotests/118.out
--
2.6.2
next reply other threads:[~2015-11-06 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 15:27 Max Reitz [this message]
2015-11-06 15:27 ` [Qemu-devel] [PATCH v9 11/15] qmp: Introduce blockdev-change-medium Max Reitz
2015-11-10 12:48 ` Kevin Wolf
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=1446823626-12525-1-git-send-email-mreitz@redhat.com \
--to=mreitz@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).