Re: [RESEND] spufs: use timespec64 for timestamps

2018-01-21 Thread Michael Ellerman
On Tue, 2018-01-16 at 17:00:35 UTC, Arnd Bergmann wrote: > The switch log prints the tv_sec portion of timespec as a 32-bit > number, while overflows in 2106. It also uses the timespec type, > which is safe on 64-bit architectures, but deprecated because > it causes overflows in 2038 elsewhere. >

Re: [PATCH] [RESEND] spufs: use timespec64 for timestamps

2018-01-16 Thread Arnd Bergmann
On Tue, Jan 16, 2018 at 8:07 PM, Jeremy Kerr wrote: > Hi Arnd, > >> The switch log prints the tv_sec portion of timespec as a 32-bit >> number, while overflows in 2106. It also uses the timespec type, >> which is safe on 64-bit architectures, but deprecated because >> it causes overflows in 2038 e

Re: [PATCH] [RESEND] spufs: use timespec64 for timestamps

2018-01-16 Thread Jeremy Kerr
Hi Arnd, > The switch log prints the tv_sec portion of timespec as a 32-bit > number, while overflows in 2106. It also uses the timespec type, > which is safe on 64-bit architectures, but deprecated because > it causes overflows in 2038 elsewhere. > > This changes it to timespec64 and printing a

[PATCH] [RESEND] spufs: use timespec64 for timestamps

2018-01-16 Thread Arnd Bergmann
The switch log prints the tv_sec portion of timespec as a 32-bit number, while overflows in 2106. It also uses the timespec type, which is safe on 64-bit architectures, but deprecated because it causes overflows in 2038 elsewhere. This changes it to timespec64 and printing a 64-bit number for cons