qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/2] block: driver should override flags in bdrv_open()
Date: Wed, 03 Jun 2015 21:49:33 +0200	[thread overview]
Message-ID: <556F5A4D.50903@redhat.com> (raw)
In-Reply-To: <1426791197-7793-1-git-send-email-mreitz@redhat.com>

Hello and welcome to my two-monthly ping. Here it is: Ping!

On 19.03.2015 19:53, Max Reitz wrote:
> BDRV_O_PROTOCOL is an internal qemu flag which a user should be able to
> override by explicitly specifying a block driver. This series implements
> this and adds two iotests (one for NBD, one for file) to test it.
>
>
> v2 (rebase on current master):
> - Patch 1: Conflict in iotest 051's reference output (in a line that is
>    removed by this patch anyway)
>
>
> git-backport-diff against v1:
>
> 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/2:[0002] [FC] 'block: driver should override flags in bdrv_open()'
> 002/2:[----] [-C] 'iotests: Add tests for overriding BDRV_O_PROTOCOL'
>
>
> Max Reitz (2):
>    block: driver should override flags in bdrv_open()
>    iotests: Add tests for overriding BDRV_O_PROTOCOL
>
>   block.c                    | 49 +++++++++++++++++++++-------------
>   tests/qemu-iotests/051     |  1 -
>   tests/qemu-iotests/051.out |  3 ---
>   tests/qemu-iotests/119     | 60 ++++++++++++++++++++++++++++++++++++++++++
>   tests/qemu-iotests/119.out | 11 ++++++++
>   tests/qemu-iotests/120     | 65 ++++++++++++++++++++++++++++++++++++++++++++++
>   tests/qemu-iotests/120.out | 15 +++++++++++
>   tests/qemu-iotests/group   |  2 ++
>   8 files changed, 184 insertions(+), 22 deletions(-)
>   create mode 100755 tests/qemu-iotests/119
>   create mode 100644 tests/qemu-iotests/119.out
>   create mode 100755 tests/qemu-iotests/120
>   create mode 100644 tests/qemu-iotests/120.out

  parent reply	other threads:[~2015-06-03 19:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19 18:53 [Qemu-devel] [PATCH v2 0/2] block: driver should override flags in bdrv_open() Max Reitz
2015-03-19 18:53 ` [Qemu-devel] [PATCH v2 1/2] " Max Reitz
2015-03-19 18:53 ` [Qemu-devel] [PATCH v2 2/2] iotests: Add tests for overriding BDRV_O_PROTOCOL Max Reitz
2015-04-24 14:37 ` [Qemu-devel] [PATCH v2 0/2] block: driver should override flags in bdrv_open() Max Reitz
2015-06-03 19:49 ` Max Reitz [this message]
2015-06-09  8:41 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2015-06-09  8:59   ` Kevin Wolf
2015-06-09 10:19     ` Stefan Hajnoczi
2015-06-09 11:36       ` Kevin Wolf
2015-06-09 11:49       ` Eric Blake
2015-06-09 14:48         ` Stefan Hajnoczi
2015-06-09 15:21           ` Eric Blake
2015-06-10  8:37             ` Kevin Wolf
2015-06-11  8:27               ` Stefan Hajnoczi
2015-06-12 14:36 ` [Qemu-devel] " 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=556F5A4D.50903@redhat.com \
    --to=mreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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).