From: John Stultz <johnstul@us.ibm.com>
To: Richard Cochran <richardcochran@gmail.com>
Cc: Ben Hutchings <ben@decadent.org.uk>,
Jonathan Nieder <jrnieder@gmail.com>,
stable@vger.kernel.org, Sasha Levin <levinsasha928@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Dave Jones <davej@redhat.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -stable] ntp: Correct TAI offset during leap second
Date: Wed, 20 Jun 2012 09:42:59 -0700 [thread overview]
Message-ID: <4FE1FD93.9050508@us.ibm.com> (raw)
In-Reply-To: <20120620162528.GB2180@netboy.at.omicron.at>
On 06/20/2012 09:25 AM, Richard Cochran wrote:
> On Tue, Jun 19, 2012 at 10:26:49AM -0700, John Stultz wrote:
>> Richard, are you planning on taking another go at those changes? Or
>> were my last suggestions just too daft? ;)
> I wonder if it is really worth the effort to fix up adjtimex.
>
> But I am strongly in favor of adding CLOCK_TAI, since that would be
> easy to add (as you showed), is free from the tick issue, and would be
> really useful for Test and Measurement style applications
I've got the CLOCK_TAI patches queued for 3.6. I should send them to
-tip soon here.
thanks
-john
next prev parent reply other threads:[~2012-06-20 16:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 18:56 [PATCH -stable] ntp: Correct TAI offset during leap second John Stultz
2012-06-15 19:01 ` John Stultz
2012-06-17 14:43 ` Ben Hutchings
2012-06-17 16:47 ` Jonathan Nieder
2012-06-17 17:34 ` Richard Cochran
2012-06-18 13:55 ` Ben Hutchings
2012-06-18 16:28 ` Richard Cochran
2012-06-19 11:54 ` Ben Hutchings
2012-06-19 17:26 ` John Stultz
2012-06-20 16:25 ` Richard Cochran
2012-06-20 16:42 ` John Stultz [this message]
2012-06-18 18:20 ` John Stultz
2012-06-19 11:57 ` Ben Hutchings
2012-07-01 1:28 ` Ben Hutchings
2012-07-01 5:27 ` John Stultz
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=4FE1FD93.9050508@us.ibm.com \
--to=johnstul@us.ibm.com \
--cc=ben@decadent.org.uk \
--cc=davej@redhat.com \
--cc=jrnieder@gmail.com \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=stable@vger.kernel.org \
--cc=tglx@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 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.