From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 0/1] NBD patches for -rc2
Date: Fri, 19 Jul 2019 15:21:18 -0500 [thread overview]
Message-ID: <20190719202119.24792-1-eblake@redhat.com> (raw)
The following changes since commit e2b47666fe1544959c89bd3ed159e9e37cc9fc73:
Merge remote-tracking branch 'remotes/berrange/tags/misc-next-pull-request' into staging (2019-07-19 14:29:13 +0100)
are available in the Git repository at:
https://repo.or.cz/qemu/ericb.git tags/pull-nbd-2019-07-19
for you to fetch changes up to 5cf42b1c1f75499b467701926d3c9691d27712e1:
nbd: Initialize reply on failure (2019-07-19 13:19:18 -0500)
----------------------------------------------------------------
nbd patches for 2019-07-19
- silence harmless compiler/valgrind warning
----------------------------------------------------------------
Eric Blake (1):
nbd: Initialize reply on failure
block/nbd.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
--
2.20.1
next reply other threads:[~2019-07-19 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 20:21 Eric Blake [this message]
2019-07-19 20:21 ` [Qemu-devel] [PULL 1/1] nbd: Initialize reply on failure Eric Blake
2019-07-22 12:20 ` [Qemu-devel] [PULL 0/1] NBD patches for -rc2 Peter Maydell
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=20190719202119.24792-1-eblake@redhat.com \
--to=eblake@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 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).