qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu block <qemu-block@nongnu.org>,
	qemu-devel <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v2 0/2] block: driver should override flags in bdrv_open()
Date: Tue, 9 Jun 2015 11:19:58 +0100	[thread overview]
Message-ID: <20150609101958.GA27900@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <20150609085942.GA4329@noname.str.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2368 bytes --]

On Tue, Jun 09, 2015 at 10:59:42AM +0200, Kevin Wolf wrote:
> Am 09.06.2015 um 10:41 hat Stefan Hajnoczi geschrieben:
> > On Thu, Mar 19, 2015 at 6:53 PM, Max Reitz <mreitz@redhat.com> 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
> > 
> > Please resend and CC Kevin (for qemu-iotests and block.c).
> 
> It's only you who dropped me from CC. :-)

For sanity, can you check whether you are on the CC list in Max's second
ping message: 556F5A4D.50903@redhat.com?

I had another CC mix-up recently and want to check whether my mail tools
are dropping CCs or if it's just me being confused.

Thanks,
Stefan

[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-06-09 10:20 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 [this message]
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=20150609101958.GA27900@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=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 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).