Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sherry Sun <sherry.sun@nxp.com>,
	Frank.Li@nxp.com, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, s.hauer@pengutronix.de, festevam@gmail.com,
	shawnguo@kernel.org, daniel.baluta@nxp.com,
	dario.binacchi@amarulasolutions.com,
	alexander.stein@ew.tq-group.com, Markus.Niebel@tq-group.com,
	matthias.schiffer@tq-group.com, y.moog@phytec.de,
	josua@solid-run.com, francesco.dolcini@toradex.com,
	primoz.fiser@norik.com
Cc: imx@lists.linux.dev, kernel@pengutronix.de,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V6 2/5] arm64: dts: imx93: Extract common EVK description into shared dtsi
Date: Sun, 8 Feb 2026 11:13:55 +0100	[thread overview]
Message-ID: <9c852962-fe86-4f36-b7a5-651f43c4f338@kernel.org> (raw)
In-Reply-To: <20260204083551.2867263-3-sherry.sun@nxp.com>

On 04/02/2026 09:35, Sherry Sun wrote:
> The i.MX93 Wireless EVK reuses most of the 11x11 EVK design. To avoid
> duplication and DTS-to-DTS includes, extract the common parts into a new
> imx93-11x11-evk-common.dtsi shared by both boards.
> 
> Rename imx93-11x11-evk.dts to imx93-11x11-evk-common.dtsi and include it
> from imx93-11x11-evk.dts.
> 
> Only structural changes are introduced, with no intended functional
> impact.
> 
> Signed-off-by: Sherry Sun <sherry.sun@nxp.com>
> ---


Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>

Best regards,
Krzysztof


  parent reply	other threads:[~2026-02-08 10:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-04  8:35 [PATCH V6 0/5] arm64: dts: imx93: Add i.MX93 Wireless EVK and refactor common parts Sherry Sun
2026-02-04  8:35 ` [PATCH V6 1/5] dt-bindings: arm: fsl: Add i.MX93 Wireless EVK board Sherry Sun
2026-02-04  8:35 ` [PATCH V6 2/5] arm64: dts: imx93: Extract common EVK description into shared dtsi Sherry Sun
2026-02-04 15:27   ` Frank Li
2026-02-08 10:13   ` Krzysztof Kozlowski [this message]
2026-02-04  8:35 ` [PATCH V6 3/5] arm64: dts: imx93: Move 11x11 EVK specific parts back to imx93-11x11-evk.dts Sherry Sun
2026-02-04 15:28   ` Frank Li
2026-02-04  8:35 ` [PATCH V6 4/5] arm64: dts: imx93: Add imx93w.dtsi for i.MX93 Wireless SiP Sherry Sun
2026-02-04  8:35 ` [PATCH V6 5/5] arm64: dts: imx93: Add i.MX93 Wireless EVK board support Sherry Sun
2026-02-04 15:30   ` Frank Li
2026-02-24 20:25 ` (subset) [PATCH V6 0/5] arm64: dts: imx93: Add i.MX93 Wireless EVK and refactor common parts Frank Li

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=9c852962-fe86-4f36-b7a5-651f43c4f338@kernel.org \
    --to=krzk@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=Markus.Niebel@tq-group.com \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=conor+dt@kernel.org \
    --cc=daniel.baluta@nxp.com \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=francesco.dolcini@toradex.com \
    --cc=imx@lists.linux.dev \
    --cc=josua@solid-run.com \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.schiffer@tq-group.com \
    --cc=primoz.fiser@norik.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=sherry.sun@nxp.com \
    --cc=y.moog@phytec.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