From: Jeff Cody <jcody@redhat.com>
To: qemu-block@nongnu.org
Cc: peter.maydell@linaro.org, jcody@redhat.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL for-2.9 0/3] Block patches
Date: Fri, 31 Mar 2017 21:25:05 -0400 [thread overview]
Message-ID: <20170401012508.24665-1-jcody@redhat.com> (raw)
The following changes since commit 95b31d709ba343ad237c3630047ee7438bac4065:
Merge remote-tracking branch 'remotes/awilliam/tags/vfio-updates-20170331.0' into staging (2017-03-31 18:06:13 +0100)
are available in the git repository at:
git://github.com/codyprime/qemu-kvm-jtc.git tags/block-pull-request
for you to fetch changes up to 34634ca28688652198f77d7001c0f1e204434663:
block/curl: Check protocol prefix (2017-03-31 15:53:22 -0400)
----------------------------------------------------------------
Block patches for -rc3
----------------------------------------------------------------
Eric Blake (1):
rbd: Fix regression in legacy key/values containing escaped :
Max Reitz (2):
qapi/curl: Extend and fix blockdev-add schema
block/curl: Check protocol prefix
block/curl.c | 10 +++++
block/rbd.c | 83 +++++++++++++++++++++--------------------
qapi/block-core.json | 103 ++++++++++++++++++++++++++++++++++++++++++++++-----
3 files changed, 146 insertions(+), 50 deletions(-)
--
2.9.3
next reply other threads:[~2017-04-01 1:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-01 1:25 Jeff Cody [this message]
2017-04-01 1:25 ` [Qemu-devel] [PULL for-2.9 1/3] rbd: Fix regression in legacy key/values containing escaped : Jeff Cody
2017-04-01 1:25 ` [Qemu-devel] [PULL for-2.9 2/3] qapi/curl: Extend and fix blockdev-add schema Jeff Cody
2017-04-01 1:25 ` [Qemu-devel] [PULL for-2.9 3/3] block/curl: Check protocol prefix Jeff Cody
2017-04-03 10:15 ` [Qemu-devel] [PULL for-2.9 0/3] Block patches Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2017-05-12 14:37 Stefan Hajnoczi
2017-05-15 13:38 ` 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=20170401012508.24665-1-jcody@redhat.com \
--to=jcody@redhat.com \
--cc=peter.maydell@linaro.org \
--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).