All of lore.kernel.org
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: remove empty disable_fiq and arch_ret_to_user macros
Date: Mon, 6 Feb 2012 15:01:44 -0800	[thread overview]
Message-ID: <20120206230144.GB20333@atomide.com> (raw)
In-Reply-To: <1328562200-8810-4-git-send-email-robherring2@gmail.com>

* Rob Herring <robherring2@gmail.com> [120206 12:36]:
> From: Rob Herring <rob.herring@calxeda.com>
> 
> Now that most platforms don't need disable_fiq and arch_ret_to_user
> macros, we can remove the empty macros or empty entry-macro.S files.
> 
> Signed-off-by: Rob Herring <rob.herring@calxeda.com>

For omaps:

Acked-by: Tony Lindgren <tony@atomide.com>

  parent reply	other threads:[~2012-02-06 23:01 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 [this message]
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=20120206230144.GB20333@atomide.com \
    --to=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.