Max Filippov 01e84c70fe 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>		2015-03-04 12:07:05 +03:00
..
boot	xtensa: nommu: fix uImage load address	2014-10-21 13:28:54 +04:00
configs	xtensa: disable link optimization	2014-12-15 23:47:24 -08:00
include	xtensa: provide __NR_sync_file_range2 instead of __NR_sync_file_range	2015-03-04 12:07:05 +03:00
kernel	Xtensa improvements for 3.18:	2014-11-10 00:24:48 -08:00
lib	xtensa: clean up files to make them code-style compliant	2012-12-18 21:10:25 -08:00
mm	vm: add VM_FAULT_SIGSEGV handling support	2015-01-29 10:51:32 -08:00
oprofile	xtensa: fix oprofile building as module	2013-05-09 01:07:09 -07:00
platforms	xtensa: xtfpga: fix hardware lockup caused by LCD driver	2015-02-27 07:55:29 +03:00
variants	xtensa: remove s6000 variant and s6105 platform	2014-10-21 13:29:01 +04:00
Kconfig	xtensa: xtfpga: fix hardware lockup caused by LCD driver	2015-02-27 07:55:29 +03:00
Kconfig.debug	xtensa: disable link optimization	2014-12-15 23:47:24 -08:00
Makefile	xtensa: remove s6000 variant and s6105 platform	2014-10-21 13:29:01 +04:00