From: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>,
Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
Cc: Kurt Kanzenbach <kurt@linutronix.de>
Subject: Re: [PATCH 3/4] support: Add xpthread_mutex_pi_support_monotonic
Date: Thu, 19 Aug 2021 09:49:05 -0300 [thread overview]
Message-ID: <0ee32502-87f7-b8bf-e273-dce51d7d6c63@linaro.org> (raw)
In-Reply-To: <87zgthbyyi.fsf@oldenburg.str.redhat.com>
On 16/08/2021 05:01, Florian Weimer wrote:
> * Adhemerval Zanella via Libc-alpha:
>
>> Returns true if Priority Inheritance support CLOCK_MONOTONIC.
>
> In the past, we used support_* interfaces for general checking of system
> properties. The x* interfaces are thin wrappers around glibc functions
> that terminate the process upon error.
>
> Thanks,
> Florian
>
Fair enough, I will change it.
next prev parent reply other threads:[~2021-08-19 12:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 20:01 [PATCH 0/4] Add CLOCK_MONOTONIC support for PI mutexes Adhemerval Zanella via Libc-alpha
2021-08-11 20:01 ` [PATCH 1/4] Linux: Add FUTEX_LOCK_PI2 Adhemerval Zanella via Libc-alpha
2021-08-11 20:01 ` [PATCH 2/4] nptl: Use FUTEX_LOCK_PI2 when available Adhemerval Zanella via Libc-alpha
2021-08-12 6:42 ` Kurt Kanzenbach via Libc-alpha
2021-08-12 12:40 ` Adhemerval Zanella via Libc-alpha
2021-08-13 6:26 ` Kurt Kanzenbach via Libc-alpha
2021-08-11 20:01 ` [PATCH 3/4] support: Add xpthread_mutex_pi_support_monotonic Adhemerval Zanella via Libc-alpha
2021-08-16 8:01 ` Florian Weimer via Libc-alpha
2021-08-19 12:49 ` Adhemerval Zanella via Libc-alpha [this message]
2021-08-11 20:01 ` [PATCH 4/4] nptl: Add CLOCK_MONOTONIC support for PI mutexes Adhemerval Zanella via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0ee32502-87f7-b8bf-e273-dce51d7d6c63@linaro.org \
--to=libc-alpha@sourceware.org \
--cc=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--cc=kurt@linutronix.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 read-only IMAP folder(s) and NNTP newsgroup(s).