From: Richard Cochran <richardcochran@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Miroslav Lichvar <mlichvar@redhat.com>,
John Stultz <john.stultz@linaro.org>,
Xiongfeng Wang <wangxiongfeng2@huawei.com>,
Stephen Boyd <sboyd@kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] ntp: Avoid undefined behaviour in second_overflow()
Date: Wed, 6 Mar 2019 21:10:03 -0800 [thread overview]
Message-ID: <20190307051003.scr4us4gktenthyn@localhost> (raw)
In-Reply-To: <CAK8P3a09XrQWSBJh5-t2WhUtMGvGQRE6coGyxjNDpX2k0bAyUg@mail.gmail.com>
On Wed, Mar 06, 2019 at 02:37:21PM +0100, Arnd Bergmann wrote:
>
> There is also y2070 (many RTCs), y2100 (some other RTCs, especially
> those that assume it's a leap year), and y2106.
That's okay, Arnd. When the time comes you can come out of retirement
and cash in, doing Y2.07, Y2.1, and Y2.106K consulting ;^}
Cheers,
Richard
prev parent reply other threads:[~2019-03-07 5:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 1:28 [RFC PATCH] ntp: Avoid undefined behaviour in second_overflow() Xiongfeng Wang
2019-03-06 1:42 ` John Stultz
2019-03-06 9:54 ` Miroslav Lichvar
2019-03-06 12:29 ` Thomas Gleixner
2019-03-06 13:37 ` Arnd Bergmann
2019-03-07 5:10 ` Richard Cochran [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=20190307051003.scr4us4gktenthyn@localhost \
--to=richardcochran@gmail.com \
--cc=arnd@arndb.de \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlichvar@redhat.com \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
--cc=wangxiongfeng2@huawei.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