From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com
Subject: [Qemu-devel] [PATCH 0/3 for-2.6] more nbd fixups
Date: Tue, 5 Apr 2016 21:35:01 -0600 [thread overview]
Message-ID: <1459913704-19949-1-git-send-email-eblake@redhat.com> (raw)
Patch 1 fixes a minor bug (wrong error) on read-only exports,
patch 2 and 3 fix up the debugging traces I used to find the
root cause of patch 1. Maintainer's discretion on whether
to take all three or just patch 1 in qemu 2.6 (but debug
output improvements can't cause regressions...)
Eric Blake (3):
nbd: Return correct error for write to read-only export
nbd: Avoid bitrot in TRACE() usage
nbd: Improve debug traces on little-endian
nbd/nbd-internal.h | 15 +++++++++------
nbd/client.c | 8 ++++----
nbd/server.c | 6 ++++--
3 files changed, 17 insertions(+), 12 deletions(-)
--
2.5.5
next reply other threads:[~2016-04-06 3:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 3:35 Eric Blake [this message]
2016-04-06 3:35 ` [Qemu-devel] [PATCH 1/3] nbd: Return correct error for write to read-only export Eric Blake
2016-04-06 3:35 ` [Qemu-devel] [PATCH 2/3] nbd: Avoid bitrot in TRACE() usage Eric Blake
2016-04-06 3:35 ` [Qemu-devel] [PATCH 3/3] nbd: Improve debug traces on little-endian Eric Blake
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=1459913704-19949-1-git-send-email-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=pbonzini@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).