Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1431223

[PATCH v3 24/24] time: Delete CURRENT_TIME_SEC

From Deepa Dinamani <deepa.kernel@gmail.com>
Newsgroups linux.kernel
Subject [PATCH v3 24/24] time: Delete CURRENT_TIME_SEC
Date 2016-06-25 23:40 +0200
Message-ID <rO3t0-2bb-21@gated-at.bofh.it> (permalink)
References <rO3t0-2bb-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


All uses of CURRENT_TIME_SEC macro have been replaced by
other time functions.  This macro is also not y2038 safe.
And, all its use cases can be fulfilled by y2038 safe
ktime_get_* variants.

Signed-off-by: Deepa Dinamani <deepa.kernel@gmail.com>
Cc: John Stultz <john.stultz@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Acked-by: John Stultz <john.stultz@linaro.org>
---
 include/linux/time.h | 1 -
 1 file changed, 1 deletion(-)

diff --git a/include/linux/time.h b/include/linux/time.h
index 4cea09d..9c3f345 100644
--- a/include/linux/time.h
+++ b/include/linux/time.h
@@ -152,7 +152,6 @@ static inline bool timespec_inject_offset_valid(const struct timespec *ts)
 }
 
 #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
-- 
1.9.1

Back to linux.kernel | Previous | Next | Find similar | Unroll thread


Thread

[PATCH v3 24/24] time: Delete CURRENT_TIME_SEC Deepa Dinamani <deepa.kernel@gmail.com> - 2016-06-25 23:40 +0200

csiph-web