From: Jeff Cody <jcody@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, mitake.hitoshi@lab.ntt.co.jp,
namei.unix@gmail.com, rjones@redhat.com, kwolf@redhat.com
Subject: [Qemu-devel] [PATCH for-2.11 0/7] Code cleanup and minor fixes
Date: Tue, 8 Aug 2017 09:39:01 -0400 [thread overview]
Message-ID: <cover.1502198932.git.jcody@redhat.com> (raw)
Some minor cleanup for a few network protocols, with a few bug fixes thrown in.
I don't think there is anything in here that needs to be for 2.10, however.
Jeff Cody (7):
block/ssh: don't call libssh2_init() in block_init()
block/ssh: make compliant with coding guidelines
block/sheepdog: remove spurious NULL check
block/sheepdog: code beautification
block/curl: check error return of curl_global_init()
block/curl: fix minor memory leaks
block/curl: code cleanup to comply with coding style
block/curl.c | 124 +++++++++++++++++++++++------------------
block/sheepdog.c | 164 +++++++++++++++++++++++++++----------------------------
block/ssh.c | 72 +++++++++++++++---------
3 files changed, 199 insertions(+), 161 deletions(-)
--
2.9.4
next reply other threads:[~2017-08-08 13:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 13:39 Jeff Cody [this message]
2017-08-08 13:39 ` [Qemu-devel] [PATCH for-2.11 1/7] block/ssh: don't call libssh2_init() in block_init() Jeff Cody
2017-08-08 13:39 ` [Qemu-devel] [PATCH for-2.11 2/7] block/ssh: make compliant with coding guidelines Jeff Cody
2017-08-08 13:39 ` [Qemu-devel] [PATCH for-2.11 3/7] block/sheepdog: remove spurious NULL check Jeff Cody
2017-08-08 13:39 ` [Qemu-devel] [PATCH for-2.11 4/7] block/sheepdog: code beautification Jeff Cody
2017-08-08 13:39 ` [Qemu-devel] [PATCH for-2.11 5/7] block/curl: check error return of curl_global_init() Jeff Cody
2017-08-08 13:39 ` [Qemu-devel] [PATCH for-2.11 6/7] block/curl: fix minor memory leaks Jeff Cody
2017-08-08 13:39 ` [Qemu-devel] [PATCH for-2.11 7/7] block/curl: code cleanup to comply with coding style 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.1502198932.git.jcody@redhat.com \
--to=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=mitake.hitoshi@lab.ntt.co.jp \
--cc=namei.unix@gmail.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rjones@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).