All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 0/2] block: driver should override flags in bdrv_open()
Date: Fri, 12 Jun 2015 16:36:15 +0200	[thread overview]
Message-ID: <20150612143615.GC4079@noname.redhat.com> (raw)
In-Reply-To: <1426791197-7793-1-git-send-email-mreitz@redhat.com>

Am 19.03.2015 um 19:53 hat Max Reitz geschrieben:
> 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)

Thanks, applied to the block branch.

Kevin

      parent reply	other threads:[~2015-06-12 14:36 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
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 ` 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=20150612143615.GC4079@noname.redhat.com \
    --to=kwolf@redhat.com \
    --cc=mreitz@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 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.