From a72ae22d5d9951a97b4e3c3101cc651ef1a01da3 Mon Sep 17 00:00:00 2001 From: Florian Weimer Date: Tue, 3 Mar 2020 12:11:01 +0100 Subject: Linux: copy_file_range syscall number is always available Due to the built-in tables, __NR_copy_file_range is always defined. Reviewed-by: Adhemerval Zanella --- sysdeps/unix/sysv/linux/copy_file_range.c | 5 ----- 1 file changed, 5 deletions(-) (limited to 'sysdeps/unix') diff --git a/sysdeps/unix/sysv/linux/copy_file_range.c b/sysdeps/unix/sysv/linux/copy_file_range.c index 65597ca025..a73c89f079 100644 --- a/sysdeps/unix/sysv/linux/copy_file_range.c +++ b/sysdeps/unix/sysv/linux/copy_file_range.c @@ -25,11 +25,6 @@ copy_file_range (int infd, __off64_t *pinoff, int outfd, __off64_t *poutoff, size_t length, unsigned int flags) { -#ifdef __NR_copy_file_range return SYSCALL_CANCEL (copy_file_range, infd, pinoff, outfd, poutoff, length, flags); -#else - __set_errno (ENOSYS); - return -1; -#endif } -- cgit v1.2.3-70-g09d2