All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: patchwork-lst@pengutronix.de, NXP Linux Team <linux-imx@nxp.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>,
	Lucas Stach <l.stach@pengutronix.de>
Subject: Re: [PATCH v2 1/2] arm64: dts: imx8mq: properly describe IRQ hierarchy
Date: Fri, 1 Feb 2019 14:49:46 +0800	[thread overview]
Message-ID: <20190201064944.GM19882@dragon> (raw)
In-Reply-To: <CAOMZO5B-fo0qM7Jc8jtauJY0FKMnKBJQdjUddTwsVPb9GTtjKQ@mail.gmail.com>

On Fri, Jan 25, 2019 at 02:44:24PM -0200, Fabio Estevam wrote:
> Hi Lucas,
> 
> On Fri, Jan 25, 2019 at 2:21 PM Lucas Stach <l.stach@pengutronix.de> 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>
> 
> In order to avoid boot issues during bisection, please invert the
> order of the patches in the series, then you can add:

Two patches will go via different branches, i.e. imx/soc and imx/dt64.
Since we always send imx/soc before imx/dt64, so it should be fine.

Shawn

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-02-01  6:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-25 16:20 [PATCH v2 1/2] arm64: dts: imx8mq: properly describe IRQ hierarchy Lucas Stach
2019-01-25 16:20 ` [PATCH v2 2/2] arm64: imx8mq: select GPCv2 irqchip driver Lucas Stach
2019-01-25 16:45   ` Fabio Estevam
2019-01-25 16:44 ` [PATCH v2 1/2] arm64: dts: imx8mq: properly describe IRQ hierarchy Fabio Estevam
2019-02-01  6:49   ` Shawn Guo [this message]
2019-02-01  7:03 ` 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=20190201064944.GM19882@dragon \
    --to=shawnguo@kernel.org \
    --cc=fabio.estevam@nxp.com \
    --cc=festevam@gmail.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 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.