From: Richard Cochran <richardcochran@gmail.com>
To: Laurent Georget <laurent.georget@supelec.fr>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [patch] adjtimex.2: add explanation about ADJ_TAI action
Date: Fri, 28 Nov 2014 22:00:43 +0100 [thread overview]
Message-ID: <20141128210043.GB14432@localhost.localdomain> (raw)
In-Reply-To: <54787B5C.1080802@supelec.fr>
On Fri, Nov 28, 2014 at 02:40:44PM +0100, Laurent Georget wrote:
> @@ -101,7 +99,19 @@ combination of zero or more of the following bits:
> Ordinary users are restricted to a zero value for
> .IR modes .
> Only the superuser may set any parameters.
> +.PP
> +Support for TAI (Atomic International Time, for a complete explanation
> about
> +what it is and what is the difference between TAI and UTC, see
> +.UR http://www.bipm.org/en/bipm/tai/tai.html
> +.I BIPM
> +.UE )
> +has been added in version 2.6.29. For any clock, the TAI offset may
Not for "any clock", just for CLOCK_REALTIME.
> +be calculated by adding a value to the UTC offset which is updated when a
> +leap second is added or deleted.
> .br
> +All the offsets in the timex structure are expressed between the value
> of the
> +clock and the corresponding value (e.g. TAI offset is the difference
> between
> +the clock and the TAI, not between TAI and another value such as UTC).
The TAI offset is just (TAI - UTC). That's all.
Thanks,
Richard
next prev parent reply other threads:[~2014-11-28 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 13:40 [patch] adjtimex.2: add explanation about ADJ_TAI action Laurent Georget
2014-11-28 21:00 ` Richard Cochran [this message]
2014-11-28 23:02 ` [patch v2] " Laurent Georget
2014-11-29 9:27 ` Michael Kerrisk (man-pages)
2014-11-29 9:46 ` Laurent Georget
2014-11-29 9:32 ` Richard Cochran
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=20141128210043.GB14432@localhost.localdomain \
--to=richardcochran@gmail.com \
--cc=laurent.georget@supelec.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@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;
as well as URLs for NNTP newsgroup(s).