From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm:irqchip: IRQCHIP_DECLARE macro is now accessible
Date: Sun, 6 Sep 2015 08:45:31 +0800 [thread overview]
Message-ID: <20150906004531.GA30746@tiger> (raw)
In-Reply-To: <7212409.q6uiaM0l3x@joel-zenbook>
On Fri, Sep 04, 2015 at 04:54:21PM -0400, Joel Porquet wrote:
> On Monday, July 13, 2015 11:20:35 PM Shawn Guo wrote:
> > On Tue, Jul 07, 2015 at 04:02:53PM -0400, 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 patch adds inclusions of 'include/linux/irqchip.h' and replaces uses
> > > of macro OF_DECLARE_2 with IRQCHIP_DECLARE.
> > >
> > > Signed-off-by: Joel Porquet <joel@porquet.org>
> > > ---
> >
> > ...
> >
> > > arch/arm/mach-imx/gpc.c | 7 ++-----
> >
> > Acked-by: Shawn Guo <shawnguo@kernel.org>
> >
> > How will this patch be sent to upstream?
>
> If it's more convenient for the different maintainers affected by this patch,
> I can probably resubmit it into a series of patches that modify each file
> separately... Let me know quickly so we don't miss the merge window!
We had sent out the materials for this merge window. So if you have a
path to upstream, you'd better send this patch through that. You've
already got the ACKs from maintainers of affected platform.
Shawn
prev parent reply other threads:[~2015-09-06 0:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 20:02 [PATCH] arm:irqchip: IRQCHIP_DECLARE macro is now accessible Joel Porquet
2015-07-07 23:46 ` Krzysztof Kozlowski
2015-07-08 6:40 ` Tony Lindgren
2015-07-13 15:20 ` Shawn Guo
2015-09-04 20:54 ` Joel Porquet
2015-09-06 0:45 ` 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=20150906004531.GA30746@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).