From: Frank.Li@oss.nxp.com
To: 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>,
Shawn Guo <shawnguo@kernel.org>,
Francesco Dolcini <francesco@dolcini.it>
Cc: Frank Li <Frank.Li@nxp.com>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/2] arm64: dts: freescale: Add Toradex OSM iMX95
Date: Wed, 23 Sep 2026 16:37:58 -0400 [thread overview]
Message-ID: <179019586937.3763388.2864908684573790285.b4-ty@b4> (raw)
In-Reply-To: <20260917102011.69071-1-francesco@dolcini.it>
From: Frank Li <Frank.Li@nxp.com>
On Thu, 17 Sep 2026 12:20:07 +0200, Francesco Dolcini wrote:
> From: Francesco Dolcini <francesco.dolcini@toradex.com>
>
> This patch series adds support for the Toradex OSM iMX95 SoM and its OSM
> Development Board.
>
> The Toradex OSM iMX95 is a SoM compliant with the OSM V1.2 specification
> from SGET, based on the NXP i.MX95 SoC and available in Size L
> (45x45 mm).
>
> [...]
Applied, thanks!
[1/2] dt-bindings: arm: fsl: Add Toradex OSM iMX95
commit: 4fed69596d776c1361150839acb9e089aaa0116e
[2/2] arm64: dts: freescale: Add Toradex OSM iMX95
commit: 7cb2afdcf226b76134db909e411b915f9fb28852
Best regards,
--
Frank Li <Frank.Li@nxp.com>
prev parent reply other threads:[~2026-09-23 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 10:20 [PATCH v2 0/2] arm64: dts: freescale: Add Toradex OSM iMX95 Francesco Dolcini
2026-09-17 10:20 ` [PATCH v2 1/2] dt-bindings: arm: fsl: " Francesco Dolcini
2026-09-20 11:04 ` Krzysztof Kozlowski
2026-09-17 10:20 ` [PATCH v2 2/2] arm64: dts: freescale: " Francesco Dolcini
2026-09-23 20:37 ` Frank.Li [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=179019586937.3763388.2864908684573790285.b4-ty@b4 \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=francesco@dolcini.it \
--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=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox