[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1491613030-11599-12-git-send-email-deepa.kernel@gmail.com>
Date: Fri, 7 Apr 2017 17:57:09 -0700
From: Deepa Dinamani <deepa.kernel@...il.com>
To: linux-kernel@...r.kernel.org, akpm@...ux-foundation.org
Cc: tglx@...utronix.de, viro@...iv.linux.org.uk,
gregkh@...uxfoundation.org, andreas.dilger@...el.com,
arnd@...db.de, bfields@...ldses.org, clm@...com,
davem@...emloft.net, dsterba@...e.com, dushistov@...l.ru,
eparis@...hat.com, jaegeuk@...nel.org, jbacik@...com,
jlayton@...chiereds.net, john.stultz@...aro.org,
jsimmons@...radead.org, mingo@...hat.com, oleg.drokin@...el.com,
paul@...l-moore.com, rostedt@...dmis.org, yuchao0@...wei.com,
ceph-devel@...r.kernel.org, devel@...verdev.osuosl.org,
linux-audit@...hat.com, linux-btrfs@...r.kernel.org,
linux-cifs@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net,
linux-fsdevel@...r.kernel.org, linux-mtd@...ts.infradead.org,
linux-security-module@...r.kernel.org,
lustre-devel@...ts.lustre.org, netdev@...r.kernel.org,
samba-technical@...ts.samba.org, y2038@...ts.linaro.org
Subject: [PATCH 11/12] time: Delete CURRENT_TIME_SEC and CURRENT_TIME
All uses of CURRENT_TIME_SEC and CURRENT_TIME macros have
been replaced by other time functions. These macros are
also not y2038 safe.
And, all their use cases can be fulfilled by y2038 safe
ktime_get_* variants.
Signed-off-by: Deepa Dinamani <deepa.kernel@...il.com>
Acked-by: John Stultz <john.stultz@...aro.org>
Reviewed-by: Arnd Bergmann <arnd@...db.de>
---
include/linux/time.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/include/linux/time.h b/include/linux/time.h
index 23f0f5c..c0543f5 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
--
2.7.4
Powered by blists - more mailing lists