Re: [Y2038] [PATCH v2 23/24] time: Delete CURRENT_TIME_SEC and CURRENT_TIME macro

2016-06-22 Thread Arnd Bergmann
On Sunday, June 19, 2016 5:27:22 PM CEST Deepa Dinamani wrote:
> All uses of these macros have been replaced by other
> time functions.
> These macros are also not y2038 safe.
> And, all its use cases can be fulfilled by y2038
> safe ktime_get_* variants.
> 
> Signed-off-by: Deepa Dinamani 
> Cc: John Stultz 
> Cc: Thomas Gleixner 
> Acked-by: John Stultz 
> 

Since we can't merge patch 19 yet due to the dependency on John's tree,
this will have to wait as well.

Arnd

___
Y2038 mailing list
Y2038@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/y2038


[Y2038] [PATCH v2 23/24] time: Delete CURRENT_TIME_SEC and CURRENT_TIME macro

2016-06-19 Thread Deepa Dinamani
All uses of these macros have been replaced by other
time functions.
These macros are also not y2038 safe.
And, all its use cases can be fulfilled by y2038
safe ktime_get_* variants.

Signed-off-by: Deepa Dinamani 
Cc: John Stultz 
Cc: Thomas Gleixner 
Acked-by: John Stultz 
---
 include/linux/time.h | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/include/linux/time.h b/include/linux/time.h
index 4cea09d..a5a07c0 100644
--- a/include/linux/time.h
+++ b/include/linux/time.h
@@ -151,9 +151,6 @@ static inline bool timespec_inject_offset_valid(const 
struct timespec *ts)
return true;
 }
 
-#define CURRENT_TIME   (current_kernel_time())
-#define CURRENT_TIME_SEC   ((struct timespec) { get_seconds(), 0 })
-
 /* Some architectures do not supply their own clocksource.
  * This is mainly the case in architectures that get their
  * inter-tick times by reading the counter on their interval
-- 
1.9.1

___
Y2038 mailing list
Y2038@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/y2038