LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Xunlei Pang <pang.xunlei@linaro.org>
To: lkml <linux-kernel@vger.kernel.org>
Cc: "rtc-linux@googlegroups.com" <rtc-linux@googlegroups.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Alessandro Zummo <a.zummo@towertech.it>,
	Richard Henderson <rth@twiddle.net>,
	Uwe Kleine-Koenig <u.kleine-koenig@pengutronix.de>,
	Linus Walleij <linus.walleij@stericsson.com>,
	Fabio Estevam <fabio.estevam@freescale.com>,
	John Stultz <john.stultz@linaro.org>,
	Arnd Bergmann <arnd.bergmann@linaro.org>,
	Xunlei Pang <pang.xunlei@linaro.org>
Subject: Re: [RFC PATCH v3 0/8] Provide y2038/y2106 safe rtc_class_ops.set_mmss64()
Date: Thu, 29 Jan 2015 00:12:09 +0800	[thread overview]
Message-ID: <CADcy93WBXjHs8A3Wo4ajiRcM2CHkN0DXSR2uB8Ww5ywe5KTDdA@mail.gmail.com> (raw)
In-Reply-To: <1421770899-4136-1-git-send-email-pang.xunlei@linaro.org>

ping Alessandro

On 21 January 2015 at 00:21, Xunlei Pang <pang.xunlei@linaro.org> wrote:
> This patch series relies on a former patchset[1], it provides y2038/y2106
> safe rtc_class_ops.set_mmss64(), and converts some possible users of set_mmss()
> to use set_mmss64(), in the hope that making these users(i.e. rtc drivers)
> y2038/y2106 safe.
>
> [1] https://lkml.org/lkml/2014/11/18/218
> [2] v1: https://lkml.org/lkml/2014/11/27/341
> [3] v2: https://lkml.org/lkml/2015/1/13/403
>
> v2->v3:
> * Remove get_seconds64(), use ktime_get_real_seconds() to replace get_seconds()
> * Refine rtc-test.c
>
> Xunlei Pang (8):
>   rtc: Provide y2038 safe rtc_class_ops.set_mmss() replacement
>   rtc/test: Update driver to address y2038/y2106 issues
>   rtc/ab3100: Update driver to address y2038/y2106 issues
>   rtc/mc13xxx: Update driver to address y2038/y2106 issues
>   rtc/mxc: Modify rtc_update_alarm() not to touch the alarm time
>   rtc/mxc: Convert get_alarm_or_time()/set_alarm_or_time() to use
>     time64_t
>   rtc/mxc: Update driver to address y2038/y2106 issues
>   alpha: rtc: change to use rtc_class_ops's set_mmss64()
>
>  arch/alpha/kernel/rtc.c   |  8 +++----
>  drivers/rtc/interface.c   |  7 +++++-
>  drivers/rtc/rtc-ab3100.c  | 55 +++++++++++++++++++++++------------------------
>  drivers/rtc/rtc-mc13xxx.c | 32 ++++++++++++---------------
>  drivers/rtc/rtc-mxc.c     | 55 +++++++++++++++++------------------------------
>  drivers/rtc/rtc-test.c    | 19 ++++++++++++++--
>  drivers/rtc/systohc.c     |  5 ++++-
>  include/linux/rtc.h       |  1 +
>  8 files changed, 93 insertions(+), 89 deletions(-)
>
> --
> 1.9.1
>

  parent reply	other threads:[~2015-01-29  2:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20 16:21 Xunlei Pang
2015-01-20 16:21 ` [RFC PATCH v3 1/8] rtc: Provide y2038 safe rtc_class_ops.set_mmss() replacement Xunlei Pang
2015-01-20 16:21 ` [RFC PATCH v3 2/8] rtc/test: Update driver to address y2038/y2106 issues Xunlei Pang
2015-01-20 16:21 ` [RFC PATCH v3 3/8] rtc/ab3100: " Xunlei Pang
2015-01-21 16:55   ` [rtc-linux] " Linus Walleij
2015-01-20 16:21 ` [RFC PATCH v3 4/8] rtc/mc13xxx: " Xunlei Pang
2015-01-20 16:21 ` [RFC PATCH v3 5/8] rtc/mxc: Modify rtc_update_alarm() not to touch the alarm time Xunlei Pang
2015-01-20 16:21 ` [RFC PATCH v3 6/8] rtc/mxc: Convert get_alarm_or_time()/set_alarm_or_time() to use time64_t Xunlei Pang
2015-01-20 16:21 ` [RFC PATCH v3 7/8] rtc/mxc: Update driver to address y2038/y2106 issues Xunlei Pang
2015-01-20 16:21 ` [RFC PATCH v3 8/8] alpha: rtc: change to use rtc_class_ops's set_mmss64() Xunlei Pang
2015-01-28 16:12 ` Xunlei Pang [this message]
2015-01-28 18:27   ` [RFC PATCH v3 0/8] Provide y2038/y2106 safe rtc_class_ops.set_mmss64() Alessandro Zummo
2015-01-28 18:53     ` John Stultz
2015-03-18 17:37     ` John Stultz
2015-03-18 23:53       ` Alessandro Zummo
2015-03-19 23:29       ` Alessandro Zummo
2015-03-24 21:42         ` 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=CADcy93WBXjHs8A3Wo4ajiRcM2CHkN0DXSR2uB8Ww5ywe5KTDdA@mail.gmail.com \
    --to=pang.xunlei@linaro.org \
    --cc=a.zummo@towertech.it \
    --cc=arnd.bergmann@linaro.org \
    --cc=fabio.estevam@freescale.com \
    --cc=john.stultz@linaro.org \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rtc-linux@googlegroups.com \
    --cc=rth@twiddle.net \
    --cc=tglx@linutronix.de \
    --cc=u.kleine-koenig@pengutronix.de \
    --subject='Re: [RFC PATCH v3 0/8] Provide y2038/y2106 safe rtc_class_ops.set_mmss64()' \
    /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

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).