From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Subject: [PATCH 0/4] error: Mechanical fixes & cleanups
Date: Wed, 22 Jul 2020 10:40:44 +0200 [thread overview]
Message-ID: <20200722084048.1726105-1-armbru@redhat.com> (raw)
Markus Armbruster (4):
coccinelle/err-bad-newline: Fix for Python 3, and add patterns
error: Strip trailing '\n' from error string arguments (again)
error: Remove NULL checks on error_propagate() calls (again)
error: Use error_fatal to simplify obvious fatal errors (again)
scripts/coccinelle/err-bad-newline.cocci | 24 ++++++++++++++++++++++--
exec.c | 11 +++--------
hw/i386/intel_iommu.c | 6 +++---
hw/net/virtio-net.c | 8 ++------
hw/s390x/s390-virtio-ccw.c | 6 +-----
hw/virtio/vhost.c | 10 +++-------
migration/colo.c | 4 +---
migration/migration.c | 8 ++------
target/ppc/mmu-hash64.c | 2 +-
9 files changed, 38 insertions(+), 41 deletions(-)
--
2.26.2
next reply other threads:[~2020-07-22 8:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 8:40 Markus Armbruster [this message]
2020-07-22 8:40 ` [PATCH 1/4] coccinelle/err-bad-newline: Fix for Python 3, and add patterns Markus Armbruster
2020-07-22 13:28 ` Eric Blake
2020-07-22 8:40 ` [PATCH 2/4] error: Strip trailing '\n' from error string arguments (again) Markus Armbruster
2020-07-22 10:04 ` Philippe Mathieu-Daudé
2020-07-22 10:33 ` David Gibson
2020-07-22 12:46 ` Peter Xu
2020-07-22 8:40 ` [PATCH 3/4] error: Remove NULL checks on error_propagate() calls (again) Markus Armbruster
2020-07-22 13:31 ` Eric Blake
2020-07-23 9:14 ` Markus Armbruster
2020-07-23 13:38 ` Markus Armbruster
2020-07-23 13:42 ` Eric Blake
2020-07-22 8:40 ` [PATCH 4/4] error: Use error_fatal to simplify obvious fatal errors (again) Markus Armbruster
2020-07-22 8:42 ` David Hildenbrand
2020-07-24 13:45 ` [PATCH 0/4] error: Mechanical fixes & cleanups Markus Armbruster
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=20200722084048.1726105-1-armbru@redhat.com \
--to=armbru@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).