[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.21.1807082133130.49@nippy.intranet>
Date: Sun, 8 Jul 2018 21:45:21 +1000 (AEST)
From: Finn Thain <fthain@...egraphics.com.au>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
cc: Arnd Bergmann <arnd@...db.de>, Paul Mackerras <paulus@...ba.org>,
Michael Ellerman <mpe@...erman.id.au>,
Joshua Thompson <funaho@...ai.org>,
Mathieu Malaterre <malat@...ian.org>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Greg Ungerer <gerg@...ux-m68k.org>,
linux-m68k <linux-m68k@...ts.linux-m68k.org>,
linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
y2038 Mailman List <y2038@...ts.linaro.org>,
Meelis Roos <mroos@...ux.ee>,
Andreas Schwab <schwab@...ux-m68k.org>
Subject: Re: [PATCH 2/3] [v2] m68k: mac: use time64_t in RTC handling
On Sun, 8 Jul 2018, Geert Uytterhoeven wrote:
> On Fri, Jun 22, 2018 at 10:55 AM Arnd Bergmann <arnd@...db.de> wrote:
> > I don't think anyone so far had a strong preference here, so I went
> > with what Mathieu suggested and kept the original Mac behavior, but
> > added the WARN_ON().
>
> So, is this safe to apply?
> Especially in light of the warnings seen by Meelis with the PPC version.
>
You mean, "can we apply this and avoid warning splats?"
Meelis's result says, "no".
I forget what date the RTC gets set to when the PMU/Cuda is reset but I
suspect that timezone arithmetic in either MacOS or Linux could cause it
to end up in 1969.
So I'd prefer to see the WARN_ON() removed.
--
Powered by blists - more mailing lists