From: James Hogan <jhogan@kernel.org>
To: Baolin Wang <baolin.wang@linaro.org>
Cc: macro@linux-mips.org, ralf@linux-mips.org, chenhc@lemote.com,
kstewart@linuxfoundation.org, gregkh@linuxfoundation.org,
tglx@linutronix.de, pombredanne@nexb.com, arnd@arndb.de,
broonie@kernel.org, paul.burton@mips.com, heiko@sntech.de,
daniel.lezcano@linaro.org, viresh.kumar@linaro.org,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] MIPS: Convert read_persistent_clock() to read_persistent_clock64()
Date: Tue, 8 May 2018 23:45:19 +0100 [thread overview]
Message-ID: <20180508224519.GB14903@jamesdev> (raw)
In-Reply-To: <c26982955db16b8f790e7f5f2a5b63e42bc78192.1525682212.git.baolin.wang@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 383 bytes --]
On Mon, May 07, 2018 at 05:28:27PM +0800, Baolin Wang wrote:
> Since struct timespec is not y2038 safe on 32bit machines, this patch
> converts read_persistent_clock() to read_persistent_clock64() using
> struct timespec64, as well as converting mktime() to mktime64().
>
> Signed-off-by: Baolin Wang <baolin.wang@linaro.org>
Thanks, both applied for 4.18
Cheers
James
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2018-05-08 22:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 9:28 [PATCH v3 1/2] MIPS: Convert read_persistent_clock() to read_persistent_clock64() Baolin Wang
2018-05-07 9:28 ` [PATCH v3 2/2] MIPS: Convert update_persistent_clock() to update_persistent_clock64() Baolin Wang
2018-05-07 21:18 ` [PATCH v3 1/2] MIPS: Convert read_persistent_clock() to read_persistent_clock64() Arnd Bergmann
2018-05-08 22:45 ` James Hogan [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=20180508224519.GB14903@jamesdev \
--to=jhogan@kernel.org \
--cc=arnd@arndb.de \
--cc=baolin.wang@linaro.org \
--cc=broonie@kernel.org \
--cc=chenhc@lemote.com \
--cc=daniel.lezcano@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=paul.burton@mips.com \
--cc=pombredanne@nexb.com \
--cc=ralf@linux-mips.org \
--cc=tglx@linutronix.de \
--cc=viresh.kumar@linaro.org \
/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.