From patchwork Mon Jan 8 06:04:48 2018 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Baolin Wang X-Patchwork-Id: 856724 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Authentication-Results: ozlabs.org; spf=none (mailfrom) smtp.mailfrom=vger.kernel.org (client-ip=209.132.180.67; helo=vger.kernel.org; envelope-from=linux-rtc-owner@vger.kernel.org; receiver=) Authentication-Results: ozlabs.org; dkim=pass (1024-bit key; unprotected) header.d=linaro.org header.i=@linaro.org header.b="CxYj6W9I"; dkim-atps=neutral Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 3zFPrf3dvTz9s9Y for ; Mon, 8 Jan 2018 17:05:22 +1100 (AEDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755443AbeAHGFV (ORCPT ); Mon, 8 Jan 2018 01:05:21 -0500 Received: from mail-pg0-f68.google.com ([74.125.83.68]:33499 "EHLO mail-pg0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755386AbeAHGFU (ORCPT ); Mon, 8 Jan 2018 01:05:20 -0500 Received: by mail-pg0-f68.google.com with SMTP id i196so4915877pgd.0 for ; Sun, 07 Jan 2018 22:05:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id; bh=qLu+q94zAulmlRlF9N3R2M6HG3ro4HIWGhH8EoUF0Ic=; b=CxYj6W9IFkk9Y+ScvcQF8e/aceno95bt4gYkF5MTUQovVoFZpSwPxH/SIrpL9b1g8y qiXK70G7iMJm0CPvt9uHAgxuu/XjCFsw5VDtXTuHliY+F6lEDyuKWW+ggRHsUS798ZaC hPkfulS7Yqthq3lJwmq97nsobur9LS0TaNc30= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id; bh=qLu+q94zAulmlRlF9N3R2M6HG3ro4HIWGhH8EoUF0Ic=; b=V0ujtoBucxrCd4Ngm83IjRSMriPWOzxGDVU/hWP6fF5Biu/Cn3H89VE/0rVUgufJn+ hyApgKETt2mFy9a801FUBdf9J0nUFmp20ThjuKWCag2vSEzSTC78kMOKk9AysUxHw5Yk 9v6YcSllAGHCLOBARFQl7IXNnw45zfGKEj/PVUcvJ6vpMUiFJJnaxZV78E83vO14jdkq /jo/flrORsiTPatwtb2R8S+Mx7rqwLRj6Odj8py5a9kjug3w36YT+xADuF3n9xnNS2xq IyGwfsqjh0+k423xZh51aqb+c7KW58RKr/eHg3mmer9co+xQ3qXXOWpP5Nn0aqmVmK4F 8Q8g== X-Gm-Message-State: AKGB3mIAO0bB23sQNFb2qDF33QVbLF5LBSCk0lybIyCPd2tW3bhFJr8o /v9oiDpGWLk9IFwfeDai75vbiw== X-Google-Smtp-Source: ACJfBotvZ0amx2ZuhPcKyOQDGxJgWRH9+0intxaB2jvaGloaBdFIuDpD9s4ZxkjmxWJ79AoS5IPmMA== X-Received: by 10.101.64.6 with SMTP id f6mr8508597pgp.58.1515391520463; Sun, 07 Jan 2018 22:05:20 -0800 (PST) Received: from baolinwangubtpc.spreadtrum.com ([117.18.48.82]) by smtp.gmail.com with ESMTPSA id q5sm20468615pgn.39.2018.01.07.22.05.17 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 07 Jan 2018 22:05:19 -0800 (PST) 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-rtc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-rtc@vger.kernel.org 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;