All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: peng.fan@nxp.com
Cc: fabio.estevam@nxp.com, kernel@pengutronix.de,
	aisheng.dong@nxp.com, robh+dt@kernel.org, sboyd@kernel.org,
	linux@rempel-privat.de, jaswinder.singh@linaro.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-imx@nxp.com,
	leonard.crestez@nxp.com, daniel.baluta@nxp.com,
	l.stach@pengutronix.de, devicetree@vger.kernel.org,
	linux-clk@vger.kernel.org
Subject: Re: [PATCH V3 2/3] arm64: dts: imx8m: add mu node
Date: Tue, 23 Jun 2020 14:50:58 +0800	[thread overview]
Message-ID: <20200623065057.GP30139@dragon> (raw)
In-Reply-To: <1590999602-29482-3-git-send-email-peng.fan@nxp.com>

On Mon, Jun 01, 2020 at 04:20:01PM +0800, peng.fan@nxp.com wrote:
> From: Peng Fan <peng.fan@nxp.com>
> 
> Add mu node to let A53 could communicate with M Core.
> 
> Signed-off-by: Peng Fan <peng.fan@nxp.com>

Applied, thanks.

  parent reply	other threads:[~2020-06-23  6:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-01  8:19 [PATCH V3 0/3] imx8m: add mu support peng.fan
2020-06-01  8:19 ` peng.fan
2020-06-01  8:20 ` [PATCH V3 1/3] dt-bindings: mailbox: imx-mu: support i.MX8M peng.fan
2020-06-01  8:20   ` peng.fan
2020-06-02  5:24   ` Oleksij Rempel
2020-06-02  5:24     ` Oleksij Rempel
2020-06-02  5:26     ` Peng Fan
2020-06-02  5:26       ` Peng Fan
2020-06-03  3:10   ` Peng Fan
2020-06-03  3:10     ` Peng Fan
2020-06-01  8:20 ` [PATCH V3 2/3] arm64: dts: imx8m: add mu node peng.fan
2020-06-01  8:20   ` peng.fan
2020-06-01  9:44   ` Aisheng Dong
2020-06-01  9:44     ` Aisheng Dong
2020-06-23  6:50   ` Shawn Guo [this message]
2020-06-01  8:20 ` [PATCH V3 3/3] clk: imx8mp: add mu root clk peng.fan
2020-06-01  8:20   ` peng.fan
2020-06-23  6:53   ` 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=20200623065057.GP30139@dragon \
    --to=shawnguo@kernel.org \
    --cc=aisheng.dong@nxp.com \
    --cc=daniel.baluta@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fabio.estevam@nxp.com \
    --cc=jaswinder.singh@linaro.org \
    --cc=kernel@pengutronix.de \
    --cc=l.stach@pengutronix.de \
    --cc=leonard.crestez@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rempel-privat.de \
    --cc=peng.fan@nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@kernel.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 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.