Re: [RFC PATCH v2 2/9] time: Provide y2106 safe get_seconds() replacement

2015-01-14 Thread Xunlei Pang
On 14 January 2015 at 04:42, Thomas Gleixner wrote: > On Tue, 13 Jan 2015, Xunlei Pang wrote: > >> From: Xunlei Pang >> >> As part of addressing "y2038 problem" for in-kernel uses, this >> patch adds safe get_seconds64() using time64_t. >> >> After this patch, get_seconds() is deprecated and all

Re: [RFC PATCH v2 2/9] time: Provide y2106 safe get_seconds() replacement

2015-01-13 Thread Thomas Gleixner
On Tue, 13 Jan 2015, Xunlei Pang wrote: > From: Xunlei Pang > > As part of addressing "y2038 problem" for in-kernel uses, this > patch adds safe get_seconds64() using time64_t. > > After this patch, get_seconds() is deprecated and all its call sites > will be fixed using get_seconds64(), after

Re: [RFC PATCH v2 2/9] time: Provide y2106 safe get_seconds() replacement

2015-01-13 Thread Arnd Bergmann
On Tuesday 13 January 2015 17:17:44 Alessandro Zummo wrote: > On Tue, 13 Jan 2015 23:44:50 +0800 > Xunlei Pang wrote: > > > -EXPORT_SYMBOL(get_seconds); > > +EXPORT_SYMBOL(get_seconds64); > > Please leave get_seconds untouched > The patch leaves it in place. However, we already have ktime_get

Re: [RFC PATCH v2 2/9] time: Provide y2106 safe get_seconds() replacement

2015-01-13 Thread Alessandro Zummo
On Tue, 13 Jan 2015 23:44:50 +0800 Xunlei Pang wrote: > -EXPORT_SYMBOL(get_seconds); > +EXPORT_SYMBOL(get_seconds64); Please leave get_seconds untouched -- Best regards, Alessandro Zummo, Tower Technologies - Torino, Italy http://www.towertech.it -- To unsubscribe from this list: se

[RFC PATCH v2 2/9] time: Provide y2106 safe get_seconds() replacement

2015-01-13 Thread Xunlei Pang
From: Xunlei Pang As part of addressing "y2038 problem" for in-kernel uses, this patch adds safe get_seconds64() using time64_t. After this patch, get_seconds() is deprecated and all its call sites will be fixed using get_seconds64(), after that it can be removed. Signed-off-by: Xunlei Pang --