From: rmallon@gmail.com (Ryan Mallon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] entry-macro.S clean-up
Date: Tue, 07 Feb 2012 09:22:52 +1100 [thread overview]
Message-ID: <4F3052BC.2050505@gmail.com> (raw)
In-Reply-To: <1328562200-8810-1-git-send-email-robherring2@gmail.com>
On 07/02/12 08:03, Rob Herring wrote:
> From: Rob Herring <rob.herring@calxeda.com>
>
> With the recent MULTI_IRQ_HANDLER support, many of the platform
> entry-macro.S files can be removed. This series removes empty
> isable_fiq and arch_ret_to_user macros from most platforms.
>
> This leaves rpc, iop13xx, iop32x and iop33x with compile time
> difference from other platforms.
>
> Rob
>
> Rob Herring (3):
> ARM: make arch_ret_to_user macro optional
> ARM: make disable_fiq macro optional
> ARM: remove empty disable_fiq and arch_ret_to_user macros
>
<snip>
> arch/arm/mach-ep93xx/include/mach/entry-macro.S | 17 ------------
Build tested only, but looks correct to me. For ep93xx:
Acked-by: Ryan Mallon <rmallon@gmail.com>
prev parent reply other threads:[~2012-02-06 22:22 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 ` [PATCH 1/3] ARM: make arch_ret_to_user macro optional Rob Herring
2012-02-06 22:21 ` 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 ` Ryan Mallon [this message]
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=4F3052BC.2050505@gmail.com \
--to=rmallon@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).