Re: [PATCH] aacraid: use timespec64 instead of timeval

Arnd, > aacraid passes the current time to the firmware in one of two ways, > either as year/month/day/... or as 32-bit unsigned seconds. > > The first one is broken on 32-bit architectures as it cannot go past > year 2038. Using timespec64 here makes it behave properly on both > 32-bit and 64-bi

RE: [PATCH] aacraid: use timespec64 instead of timeval

> > aacraid passes the current time to the firmware in one of two ways, > either as year/month/day/... or as 32-bit unsigned seconds. > > The first one is broken on 32-bit architectures as it cannot > go past year 2038. Using timespec64 here makes it behave properly > on both 32-bit and 64-bit ar