From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] arm:irchip: IRQCHIP_DECLARE macro is now accessible
Date: Tue, 13 Oct 2015 21:48:51 +0800 [thread overview]
Message-ID: <20151013134851.GA551@tiger> (raw)
In-Reply-To: <1444740975-31948-1-git-send-email-joel@porquet.org>
On Tue, Oct 13, 2015 at 02:56:12PM +0200, Joel Porquet wrote:
> The IRQCHIP_DECLARE macro migrated to 'include/linux/irqchip.h', making it
> globally accessible.
>
> See commit 91e20b5040c67c51aad88cf87db4305c5bd7f79d ("irqchip: Move
> IRQCHIP_DECLARE macro to include/linux/irqchip.h").
>
> This series of patches add inclusions of 'include/linux/irqchip.h' and
> replaces uses of macro OF_DECLARE_2 with IRQCHIP_DECLARE for platforms
> exynos, imx and omap2.
>
> I had submitted a single patch a few months ago
> (https://lkml.org/lkml/2015/7/7/1069), but it never got merged although it
> had been acked by all the subsystem maintainers. Hopefully, splitting the
> patch into these independent patches that can be applied separately should
> help.
>
> Jo?l
>
> Joel Porquet (3):
> arm:exynos: IRQCHIP_DECLARE macro is now accessible
> arm:imx: IRQCHIP_DECLARE macro is now accessible
> arm:omap2: IRQCHIP_DECLARE macro is now accessible
>
> arch/arm/mach-exynos/suspend.c | 3 ++-
> arch/arm/mach-imx/gpc.c | 7 ++-----
> arch/arm/mach-omap2/omap-wakeupgen.c | 7 ++-----
> 3 files changed, 6 insertions(+), 11 deletions(-)
Marc sent a patch [1] doing the same thing a few days ago.
Shawn
[1] http://thread.gmane.org/gmane.linux.ports.arm.kernel/444136
prev parent reply other threads:[~2015-10-13 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 12:56 [PATCH v2 0/3] arm:irchip: IRQCHIP_DECLARE macro is now accessible Joel Porquet
2015-10-13 12:56 ` [PATCH v2 1/3] arm:exynos: " Joel Porquet
2015-10-13 12:56 ` [PATCH v2 2/3] arm:imx: " Joel Porquet
2015-10-13 12:56 ` [PATCH v2 3/3] arm:omap2: " Joel Porquet
2015-10-13 13:48 ` Shawn Guo [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=20151013134851.GA551@tiger \
--to=shawnguo@kernel.org \
--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).