From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Subject: [PATCH 00/11] More miscellaneous error handling fixes
Date: Fri, 24 Apr 2020 21:20:16 +0200 [thread overview]
Message-ID: <20200424192027.11404-1-armbru@redhat.com> (raw)
Markus Armbruster (11):
nvdimm: Plug memory leak in uuid property setter
xen: Fix and improve handling of device_add usb-host errors
s390x/cpumodel: Fix harmless misuse of visit_check_struct()
s390x/pci: Fix harmless mistake in zpci's property fid's setter
tests/migration: Tighten error checking
error: Use error_reportf_err() where appropriate
mips/malta: Fix create_cps() error handling
mips/boston: Fix boston_mach_init() error handling
mips/boston: Plug memory leak in boston_mach_init()
arm/sabrelite: Consistently use &error_fatal in sabrelite_init()
i386: Fix x86_cpu_load_model() error API violation
chardev/char-socket.c | 5 +++--
hw/arm/sabrelite.c | 7 +------
hw/mem/nvdimm.c | 1 -
hw/mips/boston.c | 17 +++++++----------
hw/mips/mips_malta.c | 15 ++++++---------
hw/s390x/s390-pci-bus.c | 4 +++-
hw/sd/pxa2xx_mmci.c | 4 ++--
hw/sd/sd.c | 4 ++--
hw/usb/dev-mtp.c | 9 +++++----
hw/usb/xen-usb.c | 18 ++++++++----------
qemu-nbd.c | 7 +++----
scsi/qemu-pr-helper.c | 4 ++--
target/i386/cpu.c | 25 ++++++++++++++++---------
target/s390x/cpu_models.c | 2 +-
tests/qtest/migration-test.c | 4 ++--
15 files changed, 61 insertions(+), 65 deletions(-)
--
2.21.1
next reply other threads:[~2020-04-24 19:21 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 19:20 Markus Armbruster [this message]
2020-04-24 19:20 ` [PATCH 01/11] nvdimm: Plug memory leak in uuid property setter Markus Armbruster
2020-04-24 19:20 ` [PATCH 02/11] xen: Fix and improve handling of device_add usb-host errors Markus Armbruster
2020-04-27 7:26 ` Paul Durrant
2020-04-29 5:48 ` Markus Armbruster
2020-04-24 19:20 ` [PATCH 03/11] s390x/cpumodel: Fix harmless misuse of visit_check_struct() Markus Armbruster
2020-04-27 8:02 ` David Hildenbrand
2020-04-29 5:51 ` Markus Armbruster
2020-05-04 11:09 ` Cornelia Huck
2020-05-04 15:24 ` Markus Armbruster
2020-05-04 15:29 ` Cornelia Huck
2020-04-24 19:20 ` [PATCH 04/11] s390x/pci: Fix harmless mistake in zpci's property fid's setter Markus Armbruster
2020-04-27 14:11 ` Matthew Rosato
2020-04-27 14:40 ` Markus Armbruster
2020-04-24 19:20 ` [PATCH 05/11] tests/migration: Tighten error checking Markus Armbruster
2020-04-24 19:20 ` [PATCH 06/11] error: Use error_reportf_err() where appropriate Markus Armbruster
2020-04-24 20:08 ` Eric Blake
2020-04-27 8:53 ` Markus Armbruster
2020-04-27 9:26 ` Philippe Mathieu-Daudé
2020-04-27 13:59 ` Eric Blake
2020-04-24 19:20 ` [PATCH 07/11] mips/malta: Fix create_cps() error handling Markus Armbruster
2020-04-27 9:20 ` Philippe Mathieu-Daudé
2020-04-29 5:59 ` Markus Armbruster
2020-04-29 7:13 ` Philippe Mathieu-Daudé
2020-04-29 7:27 ` Markus Armbruster
2020-04-24 19:20 ` [PATCH 08/11] mips/boston: Fix boston_mach_init() " Markus Armbruster
2020-04-29 6:33 ` Markus Armbruster
2020-04-24 19:20 ` [PATCH 09/11] mips/boston: Plug memory leak in boston_mach_init() Markus Armbruster
2020-04-24 19:20 ` [PATCH 10/11] arm/sabrelite: Consistently use &error_fatal in sabrelite_init() Markus Armbruster
2020-04-27 9:17 ` Philippe Mathieu-Daudé
2020-04-24 19:20 ` [PATCH 11/11] i386: Fix x86_cpu_load_model() error API violation 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=20200424192027.11404-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).