[glibc] Linux: copy_file_range syscall number is always available

[Florian Weimer]

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=a72ae22d5d9951a97b4e3c3101cc651ef1a01da3

commit a72ae22d5d9951a97b4e3c3101cc651ef1a01da3
Author: Florian Weimer <fweimer@redhat.com>
Date:   Tue Mar 3 12:11:01 2020 +0100

    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 <adhemerval.zanella@linaro.org>

Diff:
---
 sysdeps/unix/sysv/linux/copy_file_range.c | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/sysdeps/unix/sysv/linux/copy_file_range.c b/sysdeps/unix/sysv/linux/copy_file_range.c
index 65597ca..a73c89f 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
 }