xtensa: provide __NR_sync_file_range2 instead of __NR_sync_file_range
authorMax Filippov <jcmvbkbc@gmail.com>
Fri, 27 Feb 2015 08:02:38 +0000 (11:02 +0300)
committerMax Filippov <jcmvbkbc@gmail.com>
Wed, 4 Mar 2015 09:07:05 +0000 (12:07 +0300)
commit01e84c70fe40c8111f960987bcf7f931842e6d07
tree34b5c4e544813578b5d449beb0bf682c548315f5
parentd44679ab13ee5f2f2b80e1bfa039a6eeb20ec41e
xtensa: provide __NR_sync_file_range2 instead of __NR_sync_file_range

xtensa actually uses sync_file_range2 implementation, so it should
define __NR_sync_file_range2 as other architectures that use that
function. That fixes userspace interface (that apparently never worked)
and avoids special-casing xtensa in libc implementations.
See the thread ending at
http://lists.busybox.net/pipermail/uclibc/2015-February/048833.html
for more details.

Cc: stable@vger.kernel.org
Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
arch/xtensa/include/uapi/asm/unistd.h