forked from Minki/linux
d33c577ccc
The time, stime, utime, utimes, and futimesat system calls are only used on older architectures, and we do not provide y2038 safe variants of them, as they are replaced by clock_gettime64, clock_settime64, and utimensat_time64. However, for consistency it seems better to have the 32-bit architectures that still use them call the "time32" entry points (leaving the traditional handlers for the 64-bit architectures), like we do for system calls that now require two versions. Note: We used to always define __ARCH_WANT_SYS_TIME and __ARCH_WANT_SYS_UTIME and only set __ARCH_WANT_COMPAT_SYS_TIME and __ARCH_WANT_SYS_UTIME32 for compat mode on 64-bit kernels. Now this is reversed: only 64-bit architectures set __ARCH_WANT_SYS_TIME/UTIME, while we need __ARCH_WANT_SYS_TIME32/UTIME32 for 32-bit architectures and compat mode. The resulting asm/unistd.h changes look a bit counterintuitive. This is only a cleanup patch and it should not change any behavior. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org> Acked-by: Heiko Carstens <heiko.carstens@de.ibm.com> |
||
|---|---|---|
| .. | ||
| syscalls | ||
| .gitignore | ||
| align.S | ||
| asm-offsets.c | ||
| coprocessor.S | ||
| entry.S | ||
| head.S | ||
| hw_breakpoint.c | ||
| irq.c | ||
| jump_label.c | ||
| Makefile | ||
| mcount.S | ||
| module.c | ||
| mxhead.S | ||
| pci-dma.c | ||
| pci.c | ||
| perf_event.c | ||
| platform.c | ||
| process.c | ||
| ptrace.c | ||
| s32c1i_selftest.c | ||
| setup.c | ||
| signal.c | ||
| smp.c | ||
| stacktrace.c | ||
| syscall.c | ||
| time.c | ||
| traps.c | ||
| vectors.S | ||
| vmlinux.lds.S | ||
| xtensa_ksyms.c | ||