From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, kraxel@redhat.com, aliguori@amazon.com
Subject: [Qemu-devel] [PATCH v2 0/5] char: Purge error_is_set()
Date: Mon, 19 May 2014 18:57:33 +0200 [thread overview]
Message-ID: <1400518658-2515-1-git-send-email-armbru@redhat.com> (raw)
This is a trivial respin of all error_is_set() patches that haven't
been applied, yet: character devices, qemu-sockets, and error_is_set()
removal.
Markus Armbruster (5):
char: Use return values instead of error_is_set(errp)
char: Clean up fragile use of error_is_set()
char: Explain qmp_chardev_add()'s unusual error handling
qemu-socket: Clean up inet_connect_opts()
error: error_is_set() is finally unused; remove
include/qapi/error.h | 6 ------
qemu-char.c | 32 ++++++++++++++++++++------------
util/error.c | 5 -----
util/qemu-sockets.c | 28 ++++++++++++++++------------
4 files changed, 36 insertions(+), 35 deletions(-)
--
1.9.0
next reply other threads:[~2014-05-19 16:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 16:57 Markus Armbruster [this message]
2014-05-19 16:57 ` [Qemu-devel] [PATCH v2 1/5] char: Use return values instead of error_is_set(errp) Markus Armbruster
2014-05-19 17:14 ` Eric Blake
2014-05-19 16:57 ` [Qemu-devel] [PATCH v2 2/5] char: Clean up fragile use of error_is_set() Markus Armbruster
2014-05-19 17:15 ` Eric Blake
2014-05-19 16:57 ` [Qemu-devel] [PATCH v2 3/5] char: Explain qmp_chardev_add()'s unusual error handling Markus Armbruster
2014-05-19 17:16 ` Eric Blake
2014-05-19 16:57 ` [Qemu-devel] [PATCH v2 4/5] qemu-socket: Clean up inet_connect_opts() Markus Armbruster
2014-05-19 16:57 ` [Qemu-devel] [PATCH v2 5/5] error: error_is_set() is finally unused; remove Markus Armbruster
2014-05-19 17:17 ` 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=1400518658-2515-1-git-send-email-armbru@redhat.com \
--to=armbru@redhat.com \
--cc=aliguori@amazon.com \
--cc=kraxel@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).