From: Markus Armbruster <armbru@redhat.com>
To: Yohei Kojima <y-koj@outlook.jp>
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
"Daniel P . Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH v3 1/4] util: Add thread-safe qemu_strerror() function
Date: Thu, 30 Mar 2023 21:06:59 +0200 [thread overview]
Message-ID: <87edp6oy7g.fsf@pond.sub.org> (raw)
In-Reply-To: <TYZPR06MB5418A6BDB94FB0D97ABA31299D8E9@TYZPR06MB5418.apcprd06.prod.outlook.com> (Yohei Kojima's message of "Fri, 31 Mar 2023 02:13:19 +0900")
Yohei Kojima <y-koj@outlook.jp> writes:
> Add qemu_strerror() which follows the POSIX specification for
> strerror(). While strerror() is not guaranteed to be thread-safe, this
> function is thread-safe.
Why not g_strerror()?
> This function is added to solve the following issue:
> https://gitlab.com/qemu-project/qemu/-/issues/416
The issue even asks for it...
> Signed-off-by: Yohei Kojima <y-koj@outlook.jp>
next prev parent reply other threads:[~2023-03-30 19:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 17:07 [PATCH v3 0/4] util: Add thread-safe qemu_strerror() function Yohei Kojima
2023-03-30 17:13 ` [PATCH v3 1/4] " Yohei Kojima
2023-03-30 19:06 ` Markus Armbruster [this message]
2023-03-31 4:00 ` Yohei Kojima
2023-04-06 8:57 ` Alex Bennée
2023-04-06 12:39 ` Yohei Kojima
2023-03-30 17:13 ` [PATCH v3 2/4] linux-user: replace strerror() function to the thread safe qemu_strerror() Yohei Kojima
2023-03-30 17:13 ` [PATCH v3 3/4] accel: " Yohei Kojima
2023-03-30 17:13 ` [PATCH v3 4/4] target/i386: " Yohei Kojima
2023-04-02 9:57 ` [PATCH v3 0/4] util: Add thread-safe qemu_strerror() function Yohei Kojima
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=87edp6oy7g.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=y-koj@outlook.jp \
/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.