From: Igor Mammedov <imammedo@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, armbru@redhat.com, aliguori@amazon.com
Subject: [Qemu-devel] [PATCH v2 0/2] vl.c: unify exit on error handling
Date: Mon, 20 Oct 2014 14:29:53 +0200 [thread overview]
Message-ID: <1413808195-7428-1-git-send-email-imammedo@redhat.com> (raw)
v2:
* s/exit_if_error/error_report_fatal/
* move error_report_fatal() into util/error.c
reduces amount of code needed for handling exit on error
for new users, turning it from 5LOC to 1 for each case.
Igor Mammedov (2):
vl.c: use single local_err throughout main()
vl.c: reduce exit on error code duplication
include/qemu/error-report.h | 2 ++
util/error.c | 24 ++++++++++++++++++++++++
vl.c | 38 +++++++-------------------------------
3 files changed, 33 insertions(+), 31 deletions(-)
--
1.9.3
next reply other threads:[~2014-10-20 12:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 12:29 Igor Mammedov [this message]
2014-10-20 12:29 ` [Qemu-devel] [PATCH v2 1/2] vl.c: use single local_err throughout main() Igor Mammedov
2014-10-20 12:29 ` [Qemu-devel] [PATCH v2 2/2] vl.c: reduce exit on error code duplication Igor Mammedov
2014-10-20 16:48 ` 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=1413808195-7428-1-git-send-email-imammedo@redhat.com \
--to=imammedo@redhat.com \
--cc=aliguori@amazon.com \
--cc=armbru@redhat.com \
--cc=peter.maydell@linaro.org \
--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).