All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>,
	peter.maydell@linaro.org, qemu-devel@nongnu.org,
	pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/2] error-report: provide error_report_exit()
Date: Tue, 16 Aug 2016 20:19:08 +0800	[thread overview]
Message-ID: <20160816121908.GA28518@al.usersys.redhat.com> (raw)
In-Reply-To: <20160816121708.GD9866@pxdev.xzpeter.org>

On Tue, 08/16 20:17, Peter Xu wrote:
> > Do we really need error_report_exit when we already have error_fatal?
> 
> error_fatal is the name of a global var, not the function.

I mean most error_report_exit(...) calls can be converted to
error_setg(&error_fatal, ...).

Fam

  reply	other threads:[~2016-08-16 12:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11  7:37 [Qemu-devel] [PATCH 0/2] error-report: introduce error_report_exit() Peter Xu
2016-08-11  7:37 ` [Qemu-devel] [PATCH 1/2] error-report: provide error_report_exit() Peter Xu
2016-08-16 11:05   ` Markus Armbruster
2016-08-16 11:53     ` Fam Zheng
2016-08-16 12:17       ` Peter Xu
2016-08-16 12:19         ` Fam Zheng [this message]
2016-08-16 14:00           ` Peter Xu
2016-08-16 14:01             ` Fam Zheng
2016-08-16 14:45             ` Markus Armbruster
2016-08-17  6:47               ` Peter Xu
2016-08-17  7:33                 ` Markus Armbruster
2016-08-17  7:38                   ` Peter Xu
2016-08-17  8:17         ` Peter Xu
2016-08-17  9:26           ` Markus Armbruster
2016-08-17  9:32             ` Peter Xu
2016-08-11  7:37 ` [Qemu-devel] [PATCH 2/2] error-report: leveraging error_report_exit() Peter Xu
2016-08-11  7:55   ` [Qemu-devel] [PATCH v2] " Peter Xu
2016-08-11  8:01     ` no-reply
2016-08-11  8:47       ` Peter Xu
2016-08-11  8:45         ` Fam Zheng
2016-08-11  8:58           ` Peter Xu
2016-08-11  7:50 ` [Qemu-devel] [PATCH 0/2] error-report: introduce error_report_exit() no-reply

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=20160816121908.GA28518@al.usersys.redhat.com \
    --to=famz@redhat.com \
    --cc=armbru@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=peterx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.