From: Shawn Guo <shawnguo@kernel.org>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: Fabio Estevam <fabio.estevam@nxp.com>,
kernel@pengutronix.de, NXP Linux Team <linux-imx@nxp.com>,
linux-arm-kernel@lists.infradead.org,
patchwork-lst@pengutronix.de
Subject: Re: [PATCH 1/2] arm64: dts: imx8mq: properly describe IRQ hierarchy
Date: Tue, 22 Jan 2019 14:29:29 +0800 [thread overview]
Message-ID: <20190122062927.GE19929@dragon> (raw)
In-Reply-To: <20190116105137.GL15808@dragon>
On Wed, Jan 16, 2019 at 06:51:39PM +0800, Shawn Guo wrote:
> On Tue, Jan 15, 2019 at 12:04:45PM +0100, Lucas Stach wrote:
> > The GPCv2 sits between most of the peripherals and the GIC and
> > functions as a wakeup controller for the CPU cores.
> >
> > Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
>
> Applied this one, thanks.
It seems that applying this patch alone causes trouble for people
playing -next. So dropped it for now.
Shawn
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-01-22 6:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 11:04 [PATCH 1/2] arm64: dts: imx8mq: properly describe IRQ hierarchy Lucas Stach
2019-01-15 11:04 ` [PATCH 2/2] arm64: imx8mq: select GPCv2 irqchip driver Lucas Stach
2019-01-21 17:45 ` Fabio Estevam
2019-01-16 10:51 ` [PATCH 1/2] arm64: dts: imx8mq: properly describe IRQ hierarchy Shawn Guo
2019-01-22 6:29 ` Shawn Guo [this message]
[not found] ` <VI1PR0402MB3357FAB48888D99A809F41AEF99F0@VI1PR0402MB3357.eurprd04.prod.outlook.com>
[not found] ` <AM6PR04MB51581FBD4D21FEFDCAC2B27FE39F0@AM6PR04MB5158.eurprd04.prod.outlook.com>
[not found] ` <7f92c150219832eb9fb54e72021116ad78ae71c3.camel@nxp.com>
2019-01-21 17:30 ` Fabio Estevam
2019-01-21 17:31 ` Lucas Stach
2019-01-21 17:34 ` Fabio Estevam
2019-01-21 17:42 ` Lucas Stach
2019-01-21 17:59 ` Daniel Baluta
2019-01-21 18:03 ` Daniel Baluta
2019-01-22 3:41 ` Manivannan Sadhasivam
2019-01-22 7:22 ` Manivannan Sadhasivam
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=20190122062927.GE19929@dragon \
--to=shawnguo@kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=patchwork-lst@pengutronix.de \
/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).