From: Helge Deller <deller@gmx.de>
To: Arnd Bergmann <arnd@arndb.de>, Baolin Wang <baolin.wang@linaro.org>
Cc: "James E.J. Bottomley" <jejb@parisc-linux.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Kate Stewart <kstewart@linuxfoundation.org>,
gregkh <gregkh@linuxfoundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Parisc List <linux-parisc@vger.kernel.org>,
Mark Brown <broonie@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] parisc: time: Convert read_persistent_clock() to read_persistent_clock64()
Date: Fri, 20 Apr 2018 20:13:38 +0200 [thread overview]
Message-ID: <7a243faa-14c8-ec8f-9f98-cda6dc58d6b3@gmx.de> (raw)
In-Reply-To: <CAK8P3a0PWLG4XZEMU2XoYiKirdq1nnkOVTLyr=S59cxvNvHuTw@mail.gmail.com>
On 20.04.2018 17:23, Arnd Bergmann wrote:
> On Thu, Apr 19, 2018 at 8:51 AM, Baolin Wang <baolin.wang@linaro.org> wrote:
>> The read_persistent_clock() uses a timespec, which is not year 2038 safe
>> on 32bit systems. On parisc architecture, we have implemented generic RTC
>> drivers that can be used to compensate the system suspend time, but the
>> RTC time can not represent the nanosecond resolution, so this patch just
>> converts to read_persistent_clock64() with timespec64.
>>
>> Signed-off-by: Baolin Wang <baolin.wang@linaro.org>
>
> I have created the exact same patch a while ago but never submitted that.
>
> If the parisc maintainers want to apply yours with my Ack, that
> would be appreciated.
>
> Acked-by: Arnd Bergmann <arnd@arndb.de>
Thanks, I'll take it through the parisc git tree.
Helge
prev parent reply other threads:[~2018-04-20 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 6:51 Baolin Wang
2018-04-20 15:23 ` Arnd Bergmann
2018-04-20 18:13 ` Helge Deller [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=7a243faa-14c8-ec8f-9f98-cda6dc58d6b3@gmx.de \
--to=deller@gmx.de \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=baolin.wang@linaro.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jejb@parisc-linux.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®