Re: [klibc] kernel/libc uapi changes for y2038

2015-05-27 Thread Arnd Bergmann
On Wednesday 27 May 2015 08:28:44 H. Peter Anvin wrote: > On 05/18/2015 02:53 AM, Arnd Bergmann wrote: > > In the patch series I posted recently [1], I introduce new system calls to > > deal > > with modified data structures, but left the question open on how these > > should > > be best accessed

Re: [klibc] kernel/libc uapi changes for y2038

2015-05-27 Thread H. Peter Anvin
On 05/18/2015 02:53 AM, Arnd Bergmann wrote: > In the patch series I posted recently [1], I introduce new system calls to > deal > with modified data structures, but left the question open on how these should > be best accessed from libc. The patches introduce a new __kernel_time64_t type > and ba

Re: [klibc] kernel/libc uapi changes for y2038

2015-05-18 Thread Thorsten Glaser
Arnd Bergmann dixit: >In the patch series I posted recently [1], I introduce new system calls to deal >with modified data structures, but left the question open on how these should >be best accessed from libc. The patches introduce a new __kernel_time64_t type Can we please have ioctls fixed for