Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Joel Porquet <joel@porquet.org>
To: Shawn Guo <shawnguo@kernel.org>
Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
	linux-samsung-soc@vger.kernel.org,
	Russell King <linux@arm.linux.org.uk>,
	Tony Lindgren <tony@atomide.com>,
	linux-kernel@vger.kernel.org, Kukjin Kim <kgene@kernel.org>,
	Sascha Hauer <kernel@pengutronix.de>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm:irqchip: IRQCHIP_DECLARE macro is now accessible
Date: Fri, 04 Sep 2015 16:54:21 -0400	[thread overview]
Message-ID: <7212409.q6uiaM0l3x@joel-zenbook> (raw)
In-Reply-To: <20150713152035.GD26642@tiger>

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!

Joël

  reply	other threads:[~2015-09-04 20:54 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 [this message]
2015-09-06  0:45     ` Shawn Guo

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=7212409.q6uiaM0l3x@joel-zenbook \
    --to=joel@porquet.org \
    --cc=k.kozlowski@samsung.com \
    --cc=kernel@pengutronix.de \
    --cc=kgene@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=shawnguo@kernel.org \
    --cc=tony@atomide.com \
    /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