On Mon, 2017-11-27 at 11:30 -0800, Deepa Dinamani wrote:
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 via ARCH_HAS_64BIT_TIME.
After this is done for all architectures, the CONFIG_64BIT_TIME symbol will be deleted.
Signed-off-by: Arnd Bergmann firstname.lastname@example.org Signed-off-by: Deepa Dinamani email@example.com
arch/Kconfig | 11 +++++++++++ 1 file changed, 11 insertions(+)
diff --git a/arch/Kconfig b/arch/Kconfig index 4f03534bfa6b..11810c29c1fa 100644 --- a/arch/Kconfig +++ b/arch/Kconfig @@ -873,6 +873,17 @@ config OLD_SIGACTION config COMPAT_OLD_SIGACTION
- def_bool n
- def_bool ARCH_HAS_64BIT_TIME
- 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
Doesn't this text belong with ARCH_HAS_64BIT_TIME?
config ARCH_NO_COHERENT_DMA_MMAP bool