From: Shuah Khan <shuah@kernel.org>
To: Benjamin Gaignard <benjamin.gaignard@linaro.org>,
john.stultz@linaro.org, tglx@linutronix.de, sboyd@codeaurora.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
patrice.chotard@st.com, a.zummo@towertech.it,
alexandre.belloni@free-electrons.com,
linux-arm-kernel@lists.infradead.org, rtc-linux@googlegroups.com
Cc: linaro-kernel@lists.linaro.org, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH v2 0/3] rtc: make st-lpc robust against y2038/2106 bug
Date: Fri, 23 Jun 2017 13:40:41 -0600 [thread overview]
Message-ID: <47b45b70-91da-ce41-535d-89d92f380274@kernel.org> (raw)
In-Reply-To: <1497864982-29284-1-git-send-email-benjamin.gaignard@linaro.org>
On 06/19/2017 03:36 AM, Benjamin Gaignard wrote:
> On 32bits platforms "struct timeval" or "time_t" are using u32 to code the
> date, this cause tools like "date" or "hwclock" failed even before setting
> the RTC device if the date is superior to year 2038 (or 2106).
>
> To avoid this problem I add one RTC test file which directly use RTC ioctl
> to set and read RTC time and alarm values.
> rtctest_setdate allow to set any date/time given in the command line.
>
> On this version 2 I add check of problematics years in rtctest like suggest
> by Alexandre.
>
> Finally that had allowed me to test and fix rtc-st-lpc driver.
>
> Benjamin Gaignard (3):
> tools: timer: add rtctest_setdate
> tool: timer: rtctest add check for problematic dates
> rtc: st-lpc: make it robust against y2038/2106 bug
>
> drivers/rtc/rtc-st-lpc.c | 19 ++--
> tools/testing/selftests/timers/Makefile | 2 +-
> tools/testing/selftests/timers/rtctest.c | 121 ++++++++++++++++++++++-
> tools/testing/selftests/timers/rtctest_setdate.c | 86 ++++++++++++++++
> 4 files changed, 212 insertions(+), 16 deletions(-)
> create mode 100644 tools/testing/selftests/timers/rtctest_setdate.c
>
Hi Thomas/John,
I can take the first two patches in this series through linux-kselftest
with your or John's Ack. Please review and let me know one way or the
other.
The third one is a rtc driver patch. Please let me know how do you want
to handle this series soon we can get this into 4.13-rc1.
thanks,
-- Shah
next prev parent reply other threads:[~2017-06-23 19:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 9:36 [PATCH v2 0/3] rtc: make st-lpc robust against y2038/2106 bug Benjamin Gaignard
2017-06-19 9:36 ` [PATCH v2 1/3] tools: timer: add rtctest_setdate Benjamin Gaignard
2017-06-19 9:36 ` [PATCH v2 2/3] tool: timer: rtctest add check for problematic dates Benjamin Gaignard
2017-06-19 9:36 ` [PATCH v2 3/3] rtc: st-lpc: make it robust against y2038/2106 bug Benjamin Gaignard
2017-06-23 19:40 ` Shuah Khan [this message]
2017-06-23 22:09 ` [PATCH v2 0/3] rtc: make st-lpc " Alexandre Belloni
2017-06-23 22:34 ` Shuah Khan
2017-07-04 11:51 ` Benjamin Gaignard
2017-07-09 20:33 ` Alexandre Belloni
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=47b45b70-91da-ce41-535d-89d92f380274@kernel.org \
--to=shuah@kernel.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=benjamin.gaignard@linaro.org \
--cc=john.stultz@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=patrice.chotard@st.com \
--cc=rtc-linux@googlegroups.com \
--cc=sboyd@codeaurora.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 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).