From: Rob Herring <robh@kernel.org>
To: Rogerio Pimentel <rpimentel.silva@gmail.com>
Cc: krzk+dt@kernel.org, conor+dt@kernel.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, alexander.stein@ew.tq-group.com,
dario.binacchi@amarulasolutions.com, marex@denx.de,
Markus.Niebel@tq-group.com, y.moog@phytec.de,
joao.goncalves@toradex.com, frieder.schrempf@kontron.de,
josua@solid-run.com, francesco.dolcini@toradex.com,
primoz.fiser@norik.com, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] dt-bindings: arm: fsl: Add i.MX8MP FRDM board
Date: Sun, 9 Nov 2025 19:04:59 -0600 [thread overview]
Message-ID: <20251110010459.GA2481668-robh@kernel.org> (raw)
In-Reply-To: <20251109214515.121742-1-rpimentel.silva@gmail.com>
On Sun, Nov 09, 2025 at 04:45:14PM -0500, Rogerio Pimentel wrote:
> Add device tree compatible string for the i.MX8MP FRDM board.
>
> Signed-off-by: Rogerio Pimentel <rpimentel.silva@gmail.com>
> ---
>
> No changes in v4
Missing Conor's ack.
>
> No changes in v3
>
> No changes in v2
>
> Documentation/devicetree/bindings/arm/fsl.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/fsl.yaml b/Documentation/devicetree/bindings/arm/fsl.yaml
> index 21b7168d61f5..f46cf6d1f502 100644
> --- a/Documentation/devicetree/bindings/arm/fsl.yaml
> +++ b/Documentation/devicetree/bindings/arm/fsl.yaml
> @@ -1099,6 +1099,7 @@ properties:
> - emcraft,imx8mp-navqp # i.MX8MP Emcraft Systems NavQ+ Kit
> - fsl,imx8mp-evk # i.MX8MP EVK Board
> - fsl,imx8mp-evk-revb4 # i.MX8MP EVK Rev B4 Board
> + - fsl,imx8mp-frdm # i.MX8MP Freedom Board
> - gateworks,imx8mp-gw71xx-2x # i.MX8MP Gateworks Board
> - gateworks,imx8mp-gw72xx-2x # i.MX8MP Gateworks Board
> - gateworks,imx8mp-gw73xx-2x # i.MX8MP Gateworks Board
> --
> 2.25.1
>
prev parent reply other threads:[~2025-11-10 1:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-09 21:45 [PATCH v4 1/2] dt-bindings: arm: fsl: Add i.MX8MP FRDM board Rogerio Pimentel
2025-11-09 21:45 ` [PATCH v4 2/2] arm64: dts: add support for NXP " Rogerio Pimentel
2025-11-10 5:15 ` Joseph Guo
2025-11-10 19:26 ` Fabio Estevam
2025-11-11 10:22 ` Daniel Baluta
2025-11-10 20:14 ` Krzysztof Kozlowski
2025-11-10 20:12 ` Krzysztof Kozlowski
2025-11-11 8:47 ` Daniel Baluta
2025-11-11 11:50 ` Fabio Estevam
2025-11-11 12:49 ` Daniel Baluta
2025-11-12 8:15 ` Daniel Baluta
2025-11-12 9:08 ` Krzysztof Kozlowski
2025-11-12 9:14 ` Krzysztof Kozlowski
2025-11-12 9:32 ` Daniel Baluta
2025-11-12 9:40 ` Krzysztof Kozlowski
2025-11-12 12:35 ` Daniel Baluta
2025-11-12 14:04 ` Rogerio Pimentel
2025-11-12 14:24 ` Krzysztof Kozlowski
2025-11-10 1:04 ` Rob Herring [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=20251110010459.GA2481668-robh@kernel.org \
--to=robh@kernel.org \
--cc=Markus.Niebel@tq-group.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=conor+dt@kernel.org \
--cc=dario.binacchi@amarulasolutions.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=frieder.schrempf@kontron.de \
--cc=imx@lists.linux.dev \
--cc=joao.goncalves@toradex.com \
--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=marex@denx.de \
--cc=primoz.fiser@norik.com \
--cc=rpimentel.silva@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).