All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Marek Vasut <marex@denx.de>
Cc: linux-arm-kernel@lists.infradead.org,
	Fabio Estevam <festevam@gmail.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	NXP Linux Team <linux-imx@nxp.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Rob Herring <robh+dt@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	devicetree@vger.kernel.org, kernel@dh-electronics.com
Subject: Re: [PATCH 1/5] arm64: dts: imx8mp: Do not delete PHY nodes on i.MX8MP DHCOM PDK2
Date: Tue, 14 Mar 2023 10:13:45 +0800	[thread overview]
Message-ID: <20230314021345.GF143566@dragon> (raw)
In-Reply-To: <20230217192647.61733-1-marex@denx.de>

On Fri, Feb 17, 2023 at 08:26:43PM +0100, Marek Vasut wrote:
> The PHY nodes may be activated via DTO in case another SoM variant
> is populated into the development kit. Do not delete the nodes.
> 
> Signed-off-by: Marek Vasut <marex@denx.de>

Applied all, thanks!

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

WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Marek Vasut <marex@denx.de>
Cc: linux-arm-kernel@lists.infradead.org,
	Fabio Estevam <festevam@gmail.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	NXP Linux Team <linux-imx@nxp.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Rob Herring <robh+dt@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	devicetree@vger.kernel.org, kernel@dh-electronics.com
Subject: Re: [PATCH 1/5] arm64: dts: imx8mp: Do not delete PHY nodes on i.MX8MP DHCOM PDK2
Date: Tue, 14 Mar 2023 10:13:45 +0800	[thread overview]
Message-ID: <20230314021345.GF143566@dragon> (raw)
In-Reply-To: <20230217192647.61733-1-marex@denx.de>

On Fri, Feb 17, 2023 at 08:26:43PM +0100, Marek Vasut wrote:
> The PHY nodes may be activated via DTO in case another SoM variant
> is populated into the development kit. Do not delete the nodes.
> 
> Signed-off-by: Marek Vasut <marex@denx.de>

Applied all, thanks!

  parent reply	other threads:[~2023-03-14  2:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17 19:26 [PATCH 1/5] arm64: dts: imx8mp: Do not delete PHY nodes on i.MX8MP DHCOM PDK2 Marek Vasut
2023-02-17 19:26 ` Marek Vasut
2023-02-17 19:26 ` [PATCH 2/5] arm64: dts: imx8mp: Adjust EQoS reset comment on i.MX8MP DHCOM Marek Vasut
2023-02-17 19:26   ` Marek Vasut
2023-02-17 19:26 ` [PATCH 3/5] arm64: dts: imx8mp: Adjust EQoS PHY address " Marek Vasut
2023-02-17 19:26   ` Marek Vasut
2023-02-17 19:26 ` [PATCH 4/5] arm64: dts: imx8mp: Add EQoS RMII pin mux " Marek Vasut
2023-02-17 19:26   ` Marek Vasut
2023-02-17 19:26 ` [PATCH 5/5] arm64: dts: imx8mp: Add FEC " Marek Vasut
2023-02-17 19:26   ` Marek Vasut
2023-03-14  2:13 ` Shawn Guo [this message]
2023-03-14  2:13   ` [PATCH 1/5] arm64: dts: imx8mp: Do not delete PHY nodes on i.MX8MP DHCOM PDK2 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=20230314021345.GF143566@dragon \
    --to=shawnguo@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@dh-electronics.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=marex@denx.de \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@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.