[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <VI1PR10MB23529E6E90A78F25A57EE5FFFE550@VI1PR10MB2352.EURPRD10.PROD.OUTLOOK.COM>
Date: Mon, 1 Apr 2019 12:42:32 +0000
From: Steve Twiss <stwiss.opensource@...semi.com>
To: Wolfram Sang <wsa@...-dreams.de>,
Alexandre Belloni <alexandre.belloni@...tlin.com>
CC: "linux-rtc@...r.kernel.org" <linux-rtc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Wolfram Sang <wsa+renesas@...g-engineering.com>,
Support Opensource <Support.Opensource@...semi.com>,
"linux-renesas-soc@...r.kernel.org"
<linux-renesas-soc@...r.kernel.org>,
Geert Uytterhoeven <geert@...ux-m68k.org>
Subject: RE: [PATCH 2/2] rtc: da9063: switch to
rtc_time64_to_tm/rtc_tm_to_time64
Hi,
On 01 April 2019 09:43, Wolfram Sang wrote:
> Subject: Re: [PATCH 2/2] rtc: da9063: switch to
> rtc_time64_to_tm/rtc_tm_to_time64
>
> On Thu, Mar 21, 2019 at 11:15:57AM +0100, Alexandre Belloni wrote:
> > Call the 64bit versions of rtc_tm time conversion now that the range is
> > enforced by the core.
> >
> > Signed-off-by: Alexandre Belloni <alexandre.belloni@...tlin.com>
>
> FWIW, RTC still works on my 32bit system:
Thanks!
> Tested-by: Wolfram Sang <wsa+renesas@...g-engineering.com>
I've also tested the RTC alarm with this patch.
It seems okay to me, no regressions.
Tested-by: Steve Twiss <stwiss.opensource@...semi.com>
Regards,
Steve
Powered by blists - more mailing lists