From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932886AbeCLRzc (ORCPT ); Mon, 12 Mar 2018 13:55:32 -0400 Received: from mail-pg0-f67.google.com ([74.125.83.67]:33358 "EHLO mail-pg0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932735AbeCLRxz (ORCPT ); Mon, 12 Mar 2018 13:53:55 -0400 X-Google-Smtp-Source: AG47ELu9uo2opRq3ULUXFXv63C8stz/em8/uufNHnR+6Cq7pmQ+VdB7HBv6CW0YPznh6+YR1bi9N/Q== From: Deepa Dinamani To: arnd@arndb.de, tglx@linutronix.de, john.stultz@linaro.org Cc: linux-kernel@vger.kernel.org, y2038@lists.linaro.org Subject: [PATCH v4 04/10] arch: introduce CONFIG_64BIT_TIME Date: Mon, 12 Mar 2018 10:53:01 -0700 Message-Id: <20180312175307.11032-5-deepa.kernel@gmail.com> X-Mailer: git-send-email 2.14.1 In-Reply-To: <20180312175307.11032-1-deepa.kernel@gmail.com> References: <20180312175307.11032-1-deepa.kernel@gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org There are a total of 53 system calls (aside from ioctl) that pass a time_t or derived data structure as an argument, and in order to extend time_t to 64-bit, we have to replace them with new system calls and keep providing backwards compatibility. To avoid adding completely new and untested code for this purpose, we introduce a new CONFIG_64BIT_TIME symbol. Every architecture that supports new 64 bit time_t syscalls enables this config. After this is done for all architectures, the CONFIG_64BIT_TIME symbol will be deleted. Signed-off-by: Arnd Bergmann Signed-off-by: Deepa Dinamani --- arch/Kconfig | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/arch/Kconfig b/arch/Kconfig index 8e0d665c8d53..16e6acfe8711 100644 --- a/arch/Kconfig +++ b/arch/Kconfig @@ -870,6 +870,14 @@ config OLD_SIGACTION config COMPAT_OLD_SIGACTION bool +config 64BIT_TIME + def_bool ARCH_HAS_64BIT_TIME + help + This should be selected by all architectures that need to support + new system calls with a 64-bit time_t. This is relevant on all 32-bit + architectures, and 64-bit architectures as part of compat syscall + handling. + config ARCH_NO_COHERENT_DMA_MMAP bool -- 2.14.1