lapi/aarch64.in: Fix incorrect syscall number for copy_file_range
PATCH 1/1 lapi/aarch64.in: Fix incorrect syscall number for copy_file_range
64-bit ARM should use the generic syscall number which is 285.
Signed-off-by Xiao Yang <[email protected]>
--- include/lapi/syscalls/aarch64.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
include/lapi/syscalls/aarch64.in +1 -1
@@ -256,4 +256,4 @@ sendmmsg 269 kcmp 272 getrandom 278 memfd_create 279 -copy_file_range 391 +copy_file_range 285
Signature · 1 line
1.8.3.1
PATCH 1/1 lapi/aarch64.in: Fix incorrect syscall number for copy_file_range
Quoted 2 lines · Xiao Yang
64-bit ARM should use the generic syscall number which is 285.
ACK. I have checked this on an aarch64 platform and confirmed.​
Quoted 26 lines
Signed-off-by Xiao Yang <[email protected]>--- include/lapi/syscalls/aarch64.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)include/lapi/syscalls/ renamed from include/lapi/syscalls/aarch64.in +0
-0aarch64.in
index 8b725e3..1f45839 100644include/lapi/syscalls/aarch64.in +1
-2@@ -256,4 +256,4 @@ sendmmsg 269 kcmp 272 getrandom 278 memfd_create 279 -copy_file_range 391 +copy_file_range 285 --1.8.3.1
--
Mailing list info: https://lists.linux.it/listinfo/ltp
Signature · 5 lines
Li Wang [email protected] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linux.it/pipermail/ltp/attachments/20180124/b5869a49/attachment.html>
PATCH 1/1 lapi/aarch64.in: Fix incorrect syscall number for copy_file_range
In reply to Xiao YangHi!
Pushed, thanks.
Signature · 2 lines
Cyril Hrubis [email protected]