From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: Eric Blake <eblake@redhat.com>, Markus Armbruster <armbru@redhat.com>
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-devel@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>,
qemu-block@nongnu.org, qemu-ppc@nongnu.org, qemu-arm@nongnu.org,
"John Snow" <jsnow@redhat.com>, "Kevin Wolf" <kwolf@redhat.com>,
"Max Reitz" <mreitz@redhat.com>,
"David Gibson" <david@gibson.dropbear.id.au>,
"Peter Crosthwaite" <crosthwaite.peter@gmail.com>,
"Alexander Graf" <agraf@suse.de>
Subject: [Qemu-devel] [PATCH v2 0/4] qapi/error: converts error_setg(&error_fatal) to error_report() + exit()
Date: Thu, 7 Jun 2018 11:46:41 -0300 [thread overview]
Message-ID: <20180607144645.10187-1-f4bug@amsat.org> (raw)
Hi,
This series converts error_setg(&error_fatal) to error_report() + exit() as
suggested by the "qapi/error.h" documentation.
This reduce Coverity and Clang static analyzer positive falses.
See http://lists.nongnu.org/archive/html/qemu-devel/2017-07/msg07585.html:
On 07/24/2017 04:52 PM, Eric Blake wrote:
That's a shame. Rather, we should patch this file (and others) to avoid
all the inconsistent uses of error_setg(&error_*), to comply with the
error.h documentation.
Since v1:
- patch #1: use assert() directly (Markus explanation)
- patch #2: use abort() without error_report() (Markus 'no lipstick')
- patch #3: replaced exit() by assert() (Markus)
- patch #4: no change, added R-b
Regards,
Phil.
Philippe Mathieu-Daudé (4):
hw/block/fdc: Replace error_setg(&error_abort) by assert()
hw/ppc/spapr_drc: Replace error_setg(&error_abort) by abort()
hw/arm/sysbus-fdt: Replace error_setg(&error_fatal) by error_report() + exit()
device_tree: Replace error_setg(&error_fatal) by error_report() + exit()
device_tree.c | 23 +++++++++++++----------
hw/arm/sysbus-fdt.c | 42 +++++++++++++++++++++++-------------------
hw/block/fdc.c | 9 +--------
hw/ppc/spapr_drc.c | 2 +-
4 files changed, 38 insertions(+), 38 deletions(-)
--
2.17.1
next reply other threads:[~2018-06-07 14:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 14:46 Philippe Mathieu-Daudé [this message]
2018-06-07 14:46 ` [Qemu-devel] [PATCH v2 1/4] hw/block/fdc: Replace error_setg(&error_abort) by assert() Philippe Mathieu-Daudé
2018-06-07 17:18 ` John Snow
2018-06-08 6:05 ` Markus Armbruster
2018-06-08 15:03 ` John Snow
2018-06-07 14:46 ` [Qemu-devel] [PATCH v2 2/4] hw/ppc/spapr_drc: Replace error_setg(&error_abort) by abort() Philippe Mathieu-Daudé
2018-06-08 3:03 ` David Gibson
2018-06-08 3:54 ` Philippe Mathieu-Daudé
2018-06-08 4:23 ` David Gibson
2018-06-08 6:22 ` Markus Armbruster
2018-06-07 14:46 ` [Qemu-devel] [PATCH v2 3/4] hw/arm/sysbus-fdt: Replace error_setg(&error_fatal) by error_report() + exit() Philippe Mathieu-Daudé
2018-06-08 6:27 ` Markus Armbruster
2018-06-21 11:14 ` Philippe Mathieu-Daudé
2018-06-07 14:46 ` [Qemu-devel] [PATCH v2 4/4] device_tree: " Philippe Mathieu-Daudé
2018-06-08 3:04 ` David Gibson
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=20180607144645.10187-1-f4bug@amsat.org \
--to=f4bug@amsat.org \
--cc=agraf@suse.de \
--cc=armbru@redhat.com \
--cc=crosthwaite.peter@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=eblake@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).