Re: [PATCH v5 0/5] Introduce current_time() api

2016-09-27 Thread Al Viro
On Wed, Sep 14, 2016 at 09:45:55AM -0700, Linus Torvalds wrote: > On Wed, Sep 14, 2016 at 7:48 AM, Deepa Dinamani > wrote: > > The series is aimed at getting rid of CURRENT_TIME and CURRENT_TIME_SEC > > macros. > > The macros are not y2038 safe. There is no plan to transition them into > > bein

Re: [PATCH v5 0/5] Introduce current_time() api

2016-09-14 Thread Linus Torvalds
On Wed, Sep 14, 2016 at 7:48 AM, Deepa Dinamani wrote: > The series is aimed at getting rid of CURRENT_TIME and CURRENT_TIME_SEC > macros. > The macros are not y2038 safe. There is no plan to transition them into being > y2038 safe. This version looks ok to me. Al, would you be willing to queue

[PATCH v5 0/5] Introduce current_time() api

2016-09-14 Thread Deepa Dinamani
The series is aimed at getting rid of CURRENT_TIME and CURRENT_TIME_SEC macros. The macros are not y2038 safe. There is no plan to transition them into being y2038 safe. ktime_get_* api's can be used in their place. And, these are y2038 safe. Thanks to Arnd Bergmann for all the guidance and discus