[PATCH 3.16 034/125] ARM: 8097/1: unistd.h: relocate comments back to place
From: Greg Kroah-Hartman
Date: Wed Sep 03 2014 - 18:17:42 EST
3.16-stable review patch. If anyone has any objections, please let me know.
From: Baruch Siach <baruch@xxxxxxxxxx>
commit bc994c77ce82576209dcf08f71de9ae51b0b100f upstream.
Commit cb8db5d45 (UAPI: (Scripted) Disintegrate arch/arm/include/asm) moved
these syscall comments out of their context into the UAPI headers. Fix this.
Fixes: cb8db5d4578a ("UAPI: (Scripted) Disintegrate arch/arm/include/asm")
Signed-off-by: Baruch Siach <baruch@xxxxxxxxxx>
Signed-off-by: Russell King <rmk+kernel@xxxxxxxxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
arch/arm/include/asm/unistd.h | 10 ++++++++++
arch/arm/include/uapi/asm/unistd.h | 11 -----------
2 files changed, 10 insertions(+), 11 deletions(-)
@@ -15,7 +15,17 @@
+ * This may need to be greater than __NR_last_syscall+1 in order to
+ * account for the padding in the syscall table
#define __NR_syscalls (384)
+ * *NOTE*: This is a ghost syscall private to the kernel. Only the
+ * __kuser_cmpxchg code in entry-armv.S should be aware of its
+ * existence. Don't ever use this from user code.
#define __ARM_NR_cmpxchg (__ARM_NR_BASE+0x00fff0)
@@ -411,11 +411,6 @@
#define __NR_renameat2 (__NR_SYSCALL_BASE+382)
- * This may need to be greater than __NR_last_syscall+1 in order to
- * account for the padding in the syscall table
* The following SWIs are ARM private.
#define __ARM_NR_BASE (__NR_SYSCALL_BASE+0x0f0000)
@@ -426,12 +421,6 @@
#define __ARM_NR_set_tls (__ARM_NR_BASE+5)
- * *NOTE*: This is a ghost syscall private to the kernel. Only the
- * __kuser_cmpxchg code in entry-armv.S should be aware of its
- * existence. Don't ever use this from user code.
* The following syscalls are obsolete and no longer available for EABI.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/