ARM: 7531/1: mark kernelmode mem{cpy,set} non-experimental

This feature was added in 2009, I've been using it off and on and
never had any problems with it on my systems. I cannot see why
it needs to be marked experimental, make it a normal feature and
let us discover its possible shortcomings as people try to turn
it on instead.

Cc: Lennert Buytenhek <kernel@wantstofly.org>
Cc: Nicolas Pitre <nico@fluxnic.net>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>

1 files changed, 2 insertions, 2 deletions

diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index e91c7cdc6fe5..aee8f3ada7ae 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -1855,8 +1855,8 @@ config ALIGNMENT_TRAP
           configuration it is safe to say N, otherwise say Y.
 
 config UACCESS_WITH_MEMCPY
-        bool "Use kernel mem{cpy,set}() for {copy_to,clear}_user() (EXPERIMENTAL)"
-        depends on MMU && EXPERIMENTAL
+        bool "Use kernel mem{cpy,set}() for {copy_to,clear}_user()"
+        depends on MMU
         default y if CPU_FEROCEON
         help
           Implement faster copy_to_user and clear_user methods for CPU