qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Jeff Cody <jcody@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, benoit.canet@irqsave.net, pkrempa@redhat.com,
	famz@redhat.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v7 for 2.1 0/2] Make 'top' optional to block commit
Date: Wed, 25 Jun 2014 13:53:12 -0600	[thread overview]
Message-ID: <53AB28A8.2090109@redhat.com> (raw)
In-Reply-To: <cover.1403723825.git.jcody@redhat.com>

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

On 06/25/2014 01:35 PM, Jeff Cody wrote:
> This is a split of the previous series "Modify block jobs to use node-names"
> 
> This series includes some function cleanup, and making 'top' optional
> for block-commit.  This in turns makes it easier for libvirt to probe
> that 2.1 supports commit of the active layer.
> 
> Jeff Cody (2):
>   block: simplify bdrv_find_base() and bdrv_find_overlay()
>   block: make 'top' argument to block-commit optional

This series is ready to go now, and should be non-controversial.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  parent reply	other threads:[~2014-06-25 19:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-25 19:35 [Qemu-devel] [PATCH v7 for 2.1 0/2] Make 'top' optional to block commit Jeff Cody
2014-06-25 19:35 ` [Qemu-devel] [PATCH v7 for 2.1 1/2] block: simplify bdrv_find_base() and bdrv_find_overlay() Jeff Cody
2014-06-25 19:35 ` [Qemu-devel] [PATCH v7 for 2.1 2/2] block: make 'top' argument to block-commit optional Jeff Cody
2014-06-30 13:14   ` [Qemu-devel] [PATCH v8 " Kevin Wolf
2014-06-25 19:41 ` [Qemu-devel] [PATCH v7 for 2.1 0/2] Make 'top' optional to block commit Jeff Cody
2014-06-25 19:53 ` Eric Blake [this message]
2014-06-30 13:09 ` Kevin Wolf
2014-06-30 15:19 ` Stefan Hajnoczi

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=53AB28A8.2090109@redhat.com \
    --to=eblake@redhat.com \
    --cc=benoit.canet@irqsave.net \
    --cc=famz@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pkrempa@redhat.com \
    --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).