Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755524AbeAHGFW (ORCPT + 1 other); Mon, 8 Jan 2018 01:05:22 -0500 Received: from mail-pg0-f67.google.com ([74.125.83.67]:46731 "EHLO mail-pg0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755407AbeAHGFV (ORCPT ); Mon, 8 Jan 2018 01:05:21 -0500 X-Google-Smtp-Source: ACJfBotvZ0amx2ZuhPcKyOQDGxJgWRH9+0intxaB2jvaGloaBdFIuDpD9s4ZxkjmxWJ79AoS5IPmMA== From: Baolin Wang To: a.zummo@towertech.it, alexandre.belloni@free-electrons.com Cc: arnd@arndb.de, broonie@kernel.org, linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org, baolin.wang@linaro.org Subject: [PATCH 1/3] rtc: Use time64_t to save range_max of RTC Date: Mon, 8 Jan 2018 14:04:48 +0800 Message-Id: X-Mailer: git-send-email 1.7.9.5 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: 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 --- 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 69e358c..4ac60af 100644 --- a/include/linux/rtc.h +++ b/include/linux/rtc.h @@ -153,7 +153,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