On 09/05/2019 23:03:40+0200, Alexandre Belloni wrote:
> Hello Linus,
>
> A huge series from me this cycle. I went through many drivers to set the
> date and time range supported by the RTC which helps solving HW
> limitation when the time comes (as early as next year for some). This
> time, I focused on drivers using .set_mms and .set_mmss64, allowing me
> to remove those callbacks. About a third of the patches got reviews, I
> actually own the RTCs and I tested another third and the remaining one
> are unlikely to cause any issues.
>
> Other than that, a single new driver and the usual fixes here and there.
>
> The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
>
> Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git tags/rtc-5.2
>
> for you to fetch changes up to dacb6a4035a010e41abaf81c1cfe2beadfb05ec8:
>
> rtc: snvs: Use __maybe_unused instead of #if CONFIG_PM_SLEEP (2019-05-08 22:14:36 +0200)
>
I forgot to mention that you will have a non trivial conflict that is
properly resolved in linux-next when you will pull arm-soc.
There is no need to check the return value of tm2bcd() after
35118b7a4ea0 ("rtc: omap: let the core handle range")
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
