Re: [PATCH] firewire: nosy: Replace timeval with timespec64

2016-03-22 Thread Stefan Richter
On Mar 21 Arnd Bergmann wrote: >>> On Sunday 20 March 2016 22:59:11 Tina Ruchandani wrote: 'struct timeval' uses a 32 bit field for its 'seconds' value which will overflow in year 2038 and beyond. This patch replaces the use of timeval in nosy.c with timespec64 which doesn't

Re: [PATCH] firewire: nosy: Replace timeval with timespec64

2016-03-22 Thread Stefan Richter
On Mar 21 Arnd Bergmann wrote: >>> On Sunday 20 March 2016 22:59:11 Tina Ruchandani wrote: 'struct timeval' uses a 32 bit field for its 'seconds' value which will overflow in year 2038 and beyond. This patch replaces the use of timeval in nosy.c with timespec64 which doesn't

Re: [PATCH] firewire: nosy: Replace timeval with timespec64

2016-03-21 Thread Arnd Bergmann
On Monday 21 March 2016 21:19:17 Stefan Richter wrote: > On Mar 21 Arnd Bergmann wrote: > > On Sunday 20 March 2016 22:59:11 Tina Ruchandani wrote: > > > 'struct timeval' uses a 32 bit field for its 'seconds' value which > > > will overflow in year 2038 and beyond. This patch replaces the use > >

Re: [PATCH] firewire: nosy: Replace timeval with timespec64

2016-03-21 Thread Arnd Bergmann
On Monday 21 March 2016 21:19:17 Stefan Richter wrote: > On Mar 21 Arnd Bergmann wrote: > > On Sunday 20 March 2016 22:59:11 Tina Ruchandani wrote: > > > 'struct timeval' uses a 32 bit field for its 'seconds' value which > > > will overflow in year 2038 and beyond. This patch replaces the use > >

Re: [PATCH] firewire: nosy: Replace timeval with timespec64

2016-03-21 Thread Stefan Richter
On Mar 21 Arnd Bergmann wrote: > On Sunday 20 March 2016 22:59:11 Tina Ruchandani wrote: > > 'struct timeval' uses a 32 bit field for its 'seconds' value which > > will overflow in year 2038 and beyond. This patch replaces the use > > of timeval in nosy.c with timespec64 which doesn't suffer from

Re: [PATCH] firewire: nosy: Replace timeval with timespec64

2016-03-21 Thread Stefan Richter
On Mar 21 Arnd Bergmann wrote: > On Sunday 20 March 2016 22:59:11 Tina Ruchandani wrote: > > 'struct timeval' uses a 32 bit field for its 'seconds' value which > > will overflow in year 2038 and beyond. This patch replaces the use > > of timeval in nosy.c with timespec64 which doesn't suffer from

Re: [PATCH] firewire: nosy: Replace timeval with timespec64

2016-03-21 Thread Arnd Bergmann
On Sunday 20 March 2016 22:59:11 Tina Ruchandani wrote: > 'struct timeval' uses a 32 bit field for its 'seconds' value which > will overflow in year 2038 and beyond. This patch replaces the use > of timeval in nosy.c with timespec64 which doesn't suffer from y2038 > issue. The code is correct as

Re: [PATCH] firewire: nosy: Replace timeval with timespec64

2016-03-21 Thread Arnd Bergmann
On Sunday 20 March 2016 22:59:11 Tina Ruchandani wrote: > 'struct timeval' uses a 32 bit field for its 'seconds' value which > will overflow in year 2038 and beyond. This patch replaces the use > of timeval in nosy.c with timespec64 which doesn't suffer from y2038 > issue. The code is correct as

[PATCH] firewire: nosy: Replace timeval with timespec64

2016-03-21 Thread Tina Ruchandani
'struct timeval' uses a 32 bit field for its 'seconds' value which will overflow in year 2038 and beyond. This patch replaces the use of timeval in nosy.c with timespec64 which doesn't suffer from y2038 issue. The code is correct as is - since it is only using the microseconds portion of timeval.

[PATCH] firewire: nosy: Replace timeval with timespec64

2016-03-21 Thread Tina Ruchandani
'struct timeval' uses a 32 bit field for its 'seconds' value which will overflow in year 2038 and beyond. This patch replaces the use of timeval in nosy.c with timespec64 which doesn't suffer from y2038 issue. The code is correct as is - since it is only using the microseconds portion of timeval.