qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: mreitz@redhat.com, eblake@redhat.com, berto@igalia.com,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v5 00/11] block: Accept node-name in all node level QMP commands
Date: Mon, 8 Aug 2016 15:14:33 +0200	[thread overview]
Message-ID: <20160808131433.GA25992@noname.str.redhat.com> (raw)
In-Reply-To: <1470223294-3870-1-git-send-email-kwolf@redhat.com>

Am 03.08.2016 um 13:21 hat Kevin Wolf geschrieben:
> As stated in the RFC I sent two weeks ago:
> 
>    * Node level commands: We need to complete the conversion that makes
>      commands accept node names instead of BlockBackend names. In some places
>      we intentionally allow only BlockBackends because we don't know if the
>      command works in other places than the root. This is okay, but we can
>      accept node names anyway. We just need to check that the node is a root
>      node as expected.
> 
> This part of the RFC is implemented by this series.

Applied to block-next.

Kevin

      parent reply	other threads:[~2016-08-08 13:14 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-03 11:21 [Qemu-devel] [PATCH v5 00/11] block: Accept node-name in all node level QMP commands Kevin Wolf
2016-08-03 11:21 ` [Qemu-devel] [PATCH v5 01/11] block: Accept node-name for block-stream Kevin Wolf
2016-08-03 12:25   ` Alberto Garcia
2016-08-03 12:53   ` Max Reitz
2016-08-03 11:21 ` [Qemu-devel] [PATCH v5 02/11] block: Accept node-name for block-commit Kevin Wolf
2016-08-03 12:32   ` Alberto Garcia
2016-08-03 12:54   ` Max Reitz
2016-08-03 11:21 ` [Qemu-devel] [PATCH v5 03/11] block: Accept node-name for blockdev-backup Kevin Wolf
2016-08-03 12:58   ` Max Reitz
2016-08-03 11:21 ` [Qemu-devel] [PATCH v5 04/11] block: Accept node-name for blockdev-mirror Kevin Wolf
2016-08-03 14:59   ` Max Reitz
2016-08-03 11:21 ` [Qemu-devel] [PATCH v5 05/11] block: Accept node-name for blockdev-snapshot-delete-internal-sync Kevin Wolf
2016-08-03 15:06   ` Max Reitz
2016-08-03 11:21 ` [Qemu-devel] [PATCH v5 06/11] block: Accept node-name for blockdev-snapshot-internal-sync Kevin Wolf
2016-08-03 15:07   ` Max Reitz
2016-08-03 11:21 ` [Qemu-devel] [PATCH v5 07/11] block: Accept node-name for change-backing-file Kevin Wolf
2016-08-03 15:09   ` Max Reitz
2016-08-03 11:21 ` [Qemu-devel] [PATCH v5 08/11] block: Accept node-name for drive-backup Kevin Wolf
2016-08-03 15:14   ` Max Reitz
2016-08-03 11:21 ` [Qemu-devel] [PATCH v5 09/11] block: Accept node-name for drive-mirror Kevin Wolf
2016-08-03 15:32   ` Max Reitz
2016-08-03 15:34   ` Max Reitz
2016-08-03 11:21 ` [Qemu-devel] [PATCH v5 10/11] nbd-server: Use a separate BlockBackend Kevin Wolf
2016-08-03 16:00   ` Max Reitz
2016-08-03 11:21 ` [Qemu-devel] [PATCH v5 11/11] nbd-server: Allow node name for nbd-server-add Kevin Wolf
2016-08-03 16:12   ` Max Reitz
2016-08-03 16:36   ` [Qemu-devel] [Qemu-block] " Max Reitz
2016-08-08 13:14 ` 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=20160808131433.GA25992@noname.str.redhat.com \
    --to=kwolf@redhat.com \
    --cc=berto@igalia.com \
    --cc=eblake@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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 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).