[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1466890668-23400-25-git-send-email-deepa.kernel@gmail.com>
Date: Sat, 25 Jun 2016 14:37:48 -0700
From: Deepa Dinamani <deepa.kernel@...il.com>
To: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: arnd@...db.de, tglx@...utronix.de, torvalds@...ux-foundation.org,
tytso@....edu, viro@...iv.linux.org.uk, y2038@...ts.linaro.org,
John Stultz <john.stultz@...aro.org>
Subject: [PATCH v3 24/24] time: Delete CURRENT_TIME_SEC
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@...il.com>
Cc: John Stultz <john.stultz@...aro.org>
Cc: Thomas Gleixner <tglx@...utronix.de>
Acked-by: John Stultz <john.stultz@...aro.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
Powered by blists - more mailing lists