Re: [PATCH] lib/date: Make rtc_mktime and mktime64 Y2038-ready

On Sun, Apr 24, 2022 at 11:34:56AM +0200, Jan Kiszka wrote: > From: Jan Kiszka > > We currently overflow due to wrong types used internally in rtc_mktime, > on all platforms, and we return a too small type on 32-bit. > > One consumer that directly benefits from this is mktime64. Many others > m

Re: [PATCH] lib/date: Make rtc_mktime and mktime64 Y2038-ready

On Sun, Apr 24, 2022 at 11:34:56AM +0200, Jan Kiszka wrote: > From: Jan Kiszka > > We currently overflow due to wrong types used internally in rtc_mktime, > on all platforms, and we return a too small type on 32-bit. > > One consumer that directly benefits from this is mktime64. Many others > m

[PATCH] lib/date: Make rtc_mktime and mktime64 Y2038-ready

From: Jan Kiszka We currently overflow due to wrong types used internally in rtc_mktime, on all platforms, and we return a too small type on 32-bit. One consumer that directly benefits from this is mktime64. Many others may still store the result in a wrong type. While at it, drop the redundant