All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	devicetree@vger.kernel.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Peng Fan <peng.fan@nxp.com>,
	Frank Li <Frank.Li@nxp.com>,
	Marc Kleine-Budde <mkl@pengutronix.de>
Subject: Re: [PATCH 0/3] arm64: dts: freescale: Use phys to replace xceiver-supply
Date: Tue, 30 Dec 2025 15:02:39 +0800	[thread overview]
Message-ID: <aVN5D6PqZVLumY89@dragon> (raw)
In-Reply-To: <20251212-imx9-can-phy-v1-0-a421d7023e13@nxp.com>

On Fri, Dec 12, 2025 at 05:57:18PM +0800, Peng Fan (OSS) wrote:
> This is a pick up of patch 6-8 from [1].
> 
> The drivers changes have been picked in 6.18, just resend the dts changes.
> 
> [1]https://lore.kernel.org/linux-phy/20251001-can-v7-0-fad29efc3884@nxp.com/
> 
> There are still some other device trees not converted to use phys,
> those will be converted later.
> 
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> Peng Fan (3):
>       arm64: dts: imx95-15x15-evk: Use phys to replace xceiver-supply
>       arm64: dts: imx8mp-evk: Use phys to replace xceiver-supply
>       arm64: dts: imx93-11x11-evk: Use phys to replace xceiver-supply

Applied all, thanks!

      parent reply	other threads:[~2025-12-30  7:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-12  9:57 [PATCH 0/3] arm64: dts: freescale: Use phys to replace xceiver-supply Peng Fan (OSS)
2025-12-12  9:57 ` [PATCH 1/3] arm64: dts: imx95-15x15-evk: " Peng Fan (OSS)
2025-12-12  9:57 ` [PATCH 2/3] arm64: dts: imx8mp-evk: " Peng Fan (OSS)
2025-12-12  9:57 ` [PATCH 3/3] arm64: dts: imx93-11x11-evk: " Peng Fan (OSS)
2025-12-12 16:46 ` [PATCH 0/3] arm64: dts: freescale: " Frank Li
2025-12-30  7:02 ` Shawn Guo [this message]

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=aVN5D6PqZVLumY89@dragon \
    --to=shawnguo@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=peng.fan@nxp.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=robh@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.