linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: make arch_ret_to_user macro optional
Date: Mon,  6 Feb 2012 15:03:18 -0600	[thread overview]
Message-ID: <1328562200-8810-2-git-send-email-robherring2@gmail.com> (raw)
In-Reply-To: <1328562200-8810-1-git-send-email-robherring2@gmail.com>

From: Rob Herring <rob.herring@calxeda.com>

Only 3 platforms need arch_ret_to_user macro, so add ARCH_HAS_RET_TO_USER
kconfig option and make iop13xx, iop32x and iop33x select it.

Signed-off-by: Rob Herring <rob.herring@calxeda.com>
---
 arch/arm/Kconfig               |    6 ++++++
 arch/arm/kernel/entry-common.S |    8 +++++++-
 2 files changed, 13 insertions(+), 1 deletions(-)

diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index a48aecc..322f2ad 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -43,6 +43,9 @@ config ARM
 config ARM_HAS_SG_CHAIN
 	bool
 
+config ARCH_HAS_RET_TO_USER
+	bool
+
 config HAVE_PWM
 	bool
 
@@ -473,6 +476,7 @@ config ARCH_H720X
 config ARCH_IOP13XX
 	bool "IOP13xx-based"
 	depends on MMU
+	select ARCH_HAS_RET_TO_USER
 	select CPU_XSC3
 	select PLAT_IOP
 	select PCI
@@ -485,6 +489,7 @@ config ARCH_IOP13XX
 config ARCH_IOP32X
 	bool "IOP32x-based"
 	depends on MMU
+	select ARCH_HAS_RET_TO_USER
 	select CPU_XSCALE
 	select PLAT_IOP
 	select PCI
@@ -496,6 +501,7 @@ config ARCH_IOP32X
 config ARCH_IOP33X
 	bool "IOP33x-based"
 	depends on MMU
+	select ARCH_HAS_RET_TO_USER
 	select CPU_XSCALE
 	select PLAT_IOP
 	select PCI
diff --git a/arch/arm/kernel/entry-common.S b/arch/arm/kernel/entry-common.S
index 9fd0ba9..5fe6ea8 100644
--- a/arch/arm/kernel/entry-common.S
+++ b/arch/arm/kernel/entry-common.S
@@ -10,9 +10,15 @@
 
 #include <asm/unistd.h>
 #include <asm/ftrace.h>
-#include <mach/entry-macro.S>
 #include <asm/unwind.h>
 
+#ifdef CONFIG_ARCH_HAS_RET_TO_USER
+#include <mach/entry-macro.S>
+#else
+	.macro  arch_ret_to_user, tmp1, tmp2
+	.endm
+#endif
+
 #include "entry-header.S"
 
 
-- 
1.7.5.4

  reply	other threads:[~2012-02-06 21:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06 21:03 [PATCH 0/3] entry-macro.S clean-up Rob Herring
2012-02-06 21:03 ` Rob Herring [this message]
2012-02-06 22:21   ` [PATCH 1/3] ARM: make arch_ret_to_user macro optional Nicolas Pitre
2012-02-06 21:03 ` [PATCH 2/3] ARM: make disable_fiq " Rob Herring
2012-02-06 22:34   ` Nicolas Pitre
2012-02-07  5:09     ` Rob Herring
2012-02-07  5:24       ` Nicolas Pitre
2012-02-07 22:52         ` Rob Herring
2012-02-08  8:38           ` Russell King - ARM Linux
2012-02-08 19:58             ` Rob Herring
2012-02-08 20:14               ` Nicolas Pitre
2012-02-08 20:30               ` Russell King - ARM Linux
2012-02-08 20:52                 ` Nicolas Pitre
2012-02-06 21:03 ` [PATCH 3/3] ARM: remove empty disable_fiq and arch_ret_to_user macros Rob Herring
2012-02-06 21:34   ` Jamie Iles
2012-02-06 22:40   ` Nicolas Pitre
2012-02-06 23:01   ` Tony Lindgren
2012-02-07  5:10   ` Linus Walleij
2012-02-07  9:35   ` Nicolas Ferre
2012-02-06 22:22 ` [PATCH 0/3] entry-macro.S clean-up Ryan Mallon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1328562200-8810-2-git-send-email-robherring2@gmail.com \
    --to=robherring2@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).