From: Jeff Cody <jcody@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, benoit.canet@irqsave.net, pkrempa@redhat.com,
famz@redhat.com, stefanha@redhat.com
Subject: [Qemu-devel] [PATCH v7 for 2.1 0/4] Use node-names for commit, stream
Date: Wed, 25 Jun 2014 15:43:11 -0400 [thread overview]
Message-ID: <cover.1403723862.git.jcody@redhat.com> (raw)
This is part 3 of the series "Modify block jobs to use node-names"
This has the auto-generated node names, and the addition of node-names
to block-commit and block-stream.
This maintains the same blocker convention that is in master, i.e. checking
the active layer blocker for commit.
Jeff Cody (4):
block: Auto-generate node_names for each BDS entry
block: Accept node-name arguments for block-commit
block: add ability for block-stream to use node-name
block: Add QMP documentation for block-stream
block.c | 16 ++++++++-
blockdev.c | 97 +++++++++++++++++++++++++++++++++++++++++++---------
hmp.c | 3 +-
qapi/block-core.json | 57 ++++++++++++++++++++++--------
qmp-commands.hx | 91 +++++++++++++++++++++++++++++++++++++++++++-----
5 files changed, 223 insertions(+), 41 deletions(-)
--
1.9.3
next reply other threads:[~2014-06-25 19:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 19:43 Jeff Cody [this message]
2014-06-25 19:43 ` [Qemu-devel] [PATCH v7 for 2.1 1/4] block: Auto-generate node_names for each BDS entry Jeff Cody
2014-06-25 19:43 ` [Qemu-devel] [PATCH v7 for 2.1 2/4] block: Accept node-name arguments for block-commit Jeff Cody
2014-06-25 19:43 ` [Qemu-devel] [PATCH v7 for 2.1 3/4] block: add ability for block-stream to use node-name Jeff Cody
2014-06-25 19:43 ` [Qemu-devel] [PATCH v7 for 2.1 4/4] block: Add QMP documentation for block-stream Jeff Cody
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=cover.1403723862.git.jcody@redhat.com \
--to=jcody@redhat.com \
--cc=benoit.canet@irqsave.net \
--cc=famz@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).