From: Kevin Wolf <kwolf@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-block@nongnu.org, jcody@redhat.com, famz@redhat.com,
qemu-devel@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/6] block: More op blocker fixes
Date: Thu, 9 Mar 2017 18:41:29 +0100 [thread overview]
Message-ID: <20170309174129.GD4910@noname.redhat.com> (raw)
In-Reply-To: <8d8b28b7-fd17-64c9-e305-59092f1f5749@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 564 bytes --]
Am 09.03.2017 um 15:23 hat Eric Blake geschrieben:
> On 03/09/2017 05:38 AM, Kevin Wolf wrote:
> > Kevin Wolf (6):
> > block: Remove check_new_perm from bdrv_replace_child()
> > block: Request block status from *file for BDRV_BLOCK_RAW
> > commit: Implement bdrv_commit_top.bdrv_co_get_block_status
> > block: Refresh filename after changing backing file
> > mirror: Implement .bdrv_refresh_filename
> > commit: Implement .bdrv_refresh_filename
> >
>
> Reviewed-by: Eric Blake <eblake@redhat.com>
Applied to the block branch.
Kevin
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2017-03-09 17:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 11:38 [Qemu-devel] [PATCH 0/6] block: More op blocker fixes Kevin Wolf
2017-03-09 11:38 ` [Qemu-devel] [PATCH 1/6] block: Remove check_new_perm from bdrv_replace_child() Kevin Wolf
2017-03-09 11:38 ` [Qemu-devel] [PATCH 2/6] block: Request block status from *file for BDRV_BLOCK_RAW Kevin Wolf
2017-03-09 11:38 ` [Qemu-devel] [PATCH 3/6] commit: Implement bdrv_commit_top.bdrv_co_get_block_status Kevin Wolf
2017-03-09 11:39 ` [Qemu-devel] [PATCH 4/6] block: Refresh filename after changing backing file Kevin Wolf
2017-03-09 11:39 ` [Qemu-devel] [PATCH 5/6] mirror: Implement .bdrv_refresh_filename Kevin Wolf
2017-03-09 11:39 ` [Qemu-devel] [PATCH 6/6] commit: " Kevin Wolf
2017-03-09 14:23 ` [Qemu-devel] [PATCH 0/6] block: More op blocker fixes Eric Blake
2017-03-09 17:41 ` Kevin Wolf [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=20170309174129.GD4910@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=jcody@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.