All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Benoît Canet" <benoit.canet@irqsave.net>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/2] Make open by reference use id then node-name
Date: Fri, 14 Feb 2014 17:03:56 +0100	[thread overview]
Message-ID: <20140214160356.GE23572@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1392221707-12916-1-git-send-email-benoit.canet@irqsave.net>

On Wed, Feb 12, 2014 at 05:15:05PM +0100, Benoît Canet wrote:
> This series was asked by Kevin.
> It sit on top of the snapshot fix patch and max openv2 series.
> 
> I have done the following tests.
> 
> check qemu-iotest ok
> snapshot blockbackend by id ok
> open quorum by node-name reference and id reference ok
> Error messages seems ok
> 
> Benoît Canet (2):
>   block: Relax bdrv_lookup_bs constraints.
>   block: Open by reference will try device then node_name.
> 
>  block.c    | 36 +++++++++++++++++++-----------------
>  blockdev.c |  6 ++++++
>  2 files changed, 25 insertions(+), 17 deletions(-)
> 
> -- 
> 1.8.3.2
> 
> 

Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block

Stefan

      parent reply	other threads:[~2014-02-14 16:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12 16:15 [Qemu-devel] [PATCH 0/2] Make open by reference use id then node-name Benoît Canet
2014-02-12 16:15 ` [Qemu-devel] [PATCH 1/2] block: Relax bdrv_lookup_bs constraints Benoît Canet
2014-02-13 18:53   ` Max Reitz
2014-02-12 16:15 ` [Qemu-devel] [PATCH 2/2] block: Open by reference will try device then node_name Benoît Canet
2014-02-13 18:54   ` Max Reitz
2014-02-14  9:57 ` [Qemu-devel] [PATCH 0/2] Make open by reference use id then node-name Kevin Wolf
2014-02-14 16:03 ` Stefan Hajnoczi [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=20140214160356.GE23572@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=benoit.canet@irqsave.net \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --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.