From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Thomas Weißschuh" <thomas@t-8ch.de>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] hw: debugexit: use runstate API instead of plain exit()
Date: Mon, 27 May 2024 18:43:50 +0200 [thread overview]
Message-ID: <ed27e6ae-164b-4aee-922e-6123e65d17ab@linaro.org> (raw)
In-Reply-To: <20240523-debugexit-v1-1-d52fcaf7bf8b@t-8ch.de>
On 23/5/24 09:09, Thomas Weißschuh wrote:
> Directly calling exit() prevents any kind of management or handling.
> Instead use the corresponding runstate API.
> The default behavior of the runstate API is the same as exit().
>
> Signed-off-by: Thomas Weißschuh <thomas@t-8ch.de>
> ---
> hw/misc/debugexit.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
prev parent reply other threads:[~2024-05-27 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 7:09 [PATCH] hw: debugexit: use runstate API instead of plain exit() Thomas Weißschuh
2024-05-27 16:43 ` Philippe Mathieu-Daudé [this message]
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=ed27e6ae-164b-4aee-922e-6123e65d17ab@linaro.org \
--to=philmd@linaro.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thomas@t-8ch.de \
/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).