From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 221186] clock_gettime CLOCK_TAI is incorrectly specified
Date: Sat, 07 Mar 2026 22:45:03 +0000 [thread overview]
Message-ID: <bug-221186-11311-YDagVl11Bn@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221186-11311@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221186
--- Comment #3 from Alejandro Colomar (alx@kernel.org) ---
Hi Paul,
On 2026-03-07T12:59:10-0800, Paul Eggert wrote:
> On 2026-03-07 06:56, Alejandro Colomar wrote:
> > BTW, Paul, would you mind reviewing this bug report and suggestion?
>
> Although it's a start, we should add more detail about TAI and leap seconds,
> and the neighboring area could use some cleanup too. Proposed patch
> attached.
Thanks a lot! I've split the patch into several atomic patches,
minimally amended, and pushed.
51a4b682 (2026-03-07; "man/man2/clock_getres.2: CLOCK_TAI: Modernize
leap-seconds documentation")
ffcf7de8 (2026-03-07; "man/man2/clock_getres.2: Clarify what "TAI" stands
for.")
0676ddff (2026-03-07; "man/man2/clock_getres.2: wfix")
78a707b1 (2026-03-07; "man/man2/clock_getres.2: Some clocks behave differently
if the system is suspended")
47e30f8e (2026-03-07; "man/man2/clock_getres.2: Clarify when clocks are
indirectly settable")
Have a lovely night!
Alex
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2026-03-07 22:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 14:21 [Bug 221186] New: clock_gettime CLOCK_TAI is incorrectly specified bugzilla-daemon
2026-03-07 14:56 ` Alejandro Colomar
2026-03-07 20:59 ` Paul Eggert
2026-03-07 22:44 ` Alejandro Colomar
2026-03-07 14:56 ` [Bug 221186] " bugzilla-daemon
2026-03-07 20:59 ` bugzilla-daemon
2026-03-07 22:45 ` bugzilla-daemon [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=bug-221186-11311-YDagVl11Bn@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-man@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox