From: Alejandro Colomar <alx@kernel.org>
To: Mark Harris <mark.hsj@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v3 1/2] man/man3/timespec_get.3: Refactor to prepare for new time bases
Date: Tue, 10 Feb 2026 23:53:04 +0100 [thread overview]
Message-ID: <aYu2wsnzbtqfXxsm@devuan> (raw)
In-Reply-To: <ec8dfdc495cb8d58e945b370658c6945cb424327.1769705123.git.mark.hsj@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2187 bytes --]
On 2026-01-29T08:52:23-0800, Mark Harris wrote:
> Add Feature Test Macro Requirements to document functions and macros
> that require ISO C11 or C23, and arrange supported time bases as a list.
>
> Signed-off-by: Mark Harris <mark.hsj@gmail.com>
Patch applied; thanks!
Cheers,
Alex
> ---
> v3: Use .TQ for time bases in STANDARDS and HISTORY
> v2: Split into two patches, add time bases to History section
>
> man/man3/timespec_get.3 | 25 ++++++++++++++++++++++---
> 1 file changed, 22 insertions(+), 3 deletions(-)
>
> diff --git a/man/man3/timespec_get.3 b/man/man3/timespec_get.3
> index 79bb82226..67da4858c 100644
> --- a/man/man3/timespec_get.3
> +++ b/man/man3/timespec_get.3
> @@ -17,6 +17,22 @@ .SH SYNOPSIS
> .BI "int timespec_get(struct timespec *" res ", int " base );
> .BI "int timespec_getres(struct timespec *" tp ", int " base );
> .fi
> +.P
> +.RS -4
> +Feature Test Macro Requirements for glibc (see
> +.BR feature_test_macros (7)):
> +.RE
> +.P
> +.BR timespec_get (),
> +.BR TIME_UTC :
> +.nf
> + _ISOC11_SOURCE
> +.fi
> +.P
> +.BR timespec_getres ():
> +.nf
> + _ISOC23_SOURCE
> +.fi
> .SH DESCRIPTION
> The
> .BR timespec_get ()
> @@ -39,16 +55,18 @@ .SH DESCRIPTION
> For a particular time base,
> the resolution is constant for the lifetime of the calling process.
> .P
> +The time base
> +.I base
> +is one of the following:
> +.TP
> .B TIME_UTC
> -is always a supported time base,
> -and is the only time base supported on Linux.
> +A system-wide time base that measures real (i.e., wall-clock) time.
> The time and resolution in this time base
> are the same as those retrieved by
> .I clock_gettime(CLOCK_REALTIME,\~res)
> and
> .IR clock_getres(CLOCK_REALTIME,\~tp) ,
> respectively.
> -Other systems may support additional time bases.
> .SH RETURN VALUE
> .BR timespec_get ()
> returns the nonzero
> @@ -78,6 +96,7 @@ .SH ATTRIBUTES
> .SH STANDARDS
> .TP
> .BR timespec_get ()
> +C23, POSIX.1-2024.
> .TQ
> .B TIME_UTC
> C23 (though ISO C doesn't specify the time epoch),
> --
> 2.52.0
>
>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-02-10 22:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 6:42 [PATCH] man/man3/timespec_get.3: Add ISO C23 time bases Mark Harris
2026-01-28 14:57 ` Alejandro Colomar
2026-01-28 17:35 ` Mark Harris
2026-01-28 17:33 ` [PATCH v2 1/2] man/man3/timespec_get.3: Refactor to prepare for new " Mark Harris
2026-01-28 17:33 ` [PATCH v2 2/2] man/man3/timespec_get.3: Add ISO C23 " Mark Harris
2026-01-29 15:28 ` [PATCH v2 1/2] man/man3/timespec_get.3: Refactor to prepare for new " Alejandro Colomar
2026-01-29 16:58 ` Mark Harris
2026-01-29 16:52 ` [PATCH v3 " Mark Harris
2026-01-29 16:52 ` [PATCH v3 2/2] man/man3/timespec_get.3: Add ISO C23 " Mark Harris
2026-02-10 23:01 ` Alejandro Colomar
2026-02-10 22:53 ` Alejandro Colomar [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=aYu2wsnzbtqfXxsm@devuan \
--to=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mark.hsj@gmail.com \
/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