Re: [Y2038] [PATCH 1/2] ppdev: convert to y2038 safe

2015-12-09 Thread Arnd Bergmann
On Wednesday 09 December 2015 14:11:37 Bamvor Jian Zhang wrote: > The y2038 issue for ppdev is changes of timeval in the ioctl > (PPSETTIME and PPGETTIME). The size of struct timeval changes from > 8bytes to 16bytes due to the changes of time_t. It lead to the > changes of the command of ioctl,

Re: [Y2038] [PATCH 1/2] ppdev: convert to y2038 safe

2015-12-09 Thread Arnd Bergmann
On Wednesday 09 December 2015 14:11:37 Bamvor Jian Zhang wrote: > The y2038 issue for ppdev is changes of timeval in the ioctl > (PPSETTIME and PPGETTIME). The size of struct timeval changes from > 8bytes to 16bytes due to the changes of time_t. It lead to the > changes of the command of ioctl,

[PATCH 1/2] ppdev: convert to y2038 safe

2015-12-08 Thread Bamvor Jian Zhang
The y2038 issue for ppdev is changes of timeval in the ioctl (PPSETTIME and PPGETTIME). The size of struct timeval changes from 8bytes to 16bytes due to the changes of time_t. It lead to the changes of the command of ioctl, e.g. for PPGETTIME, We have: on 32-bit (old): 0x80087095 on 32-bit (new):

[PATCH 1/2] ppdev: convert to y2038 safe

2015-12-08 Thread Bamvor Jian Zhang
The y2038 issue for ppdev is changes of timeval in the ioctl (PPSETTIME and PPGETTIME). The size of struct timeval changes from 8bytes to 16bytes due to the changes of time_t. It lead to the changes of the command of ioctl, e.g. for PPGETTIME, We have: on 32-bit (old): 0x80087095 on 32-bit (new):