[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <b8a475beaa4739032e3346572af2e412ebccb787.1519633350.git.baolin.wang@linaro.org>
Date: Mon, 26 Feb 2018 16:33:56 +0800
From: Baolin Wang <baolin.wang@...aro.org>
To: a.zummo@...ertech.it, alexandre.belloni@...tlin.com
Cc: arnd@...db.de, broonie@...nel.org, linux-rtc@...r.kernel.org,
linux-kernel@...r.kernel.org, baolin.wang@...aro.org,
alexandre.belloni@...e-electrons.com
Subject: [RESEND PATCH 1/3] rtc: Use time64_t to save range_max of RTC
We need use rtc->range_max to valid if the time values are valid,
and the time values are saved by time64_t type. So change the
rtc->range_max to time64_t type for comparison correctly.
Signed-off-by: Baolin Wang <baolin.wang@...aro.org>
---
include/linux/rtc.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/rtc.h b/include/linux/rtc.h
index bdfc0c4..8560282 100644
--- a/include/linux/rtc.h
+++ b/include/linux/rtc.h
@@ -152,7 +152,7 @@ struct rtc_device {
struct bin_attribute *nvram;
time64_t range_min;
- timeu64_t range_max;
+ time64_t range_max;
#ifdef CONFIG_RTC_INTF_DEV_UIE_EMUL
struct work_struct uie_task;
--
1.7.9.5
Powered by blists - more mailing lists