From: Marek Vasut <marex@denx.de>
To: linux-arm-kernel@lists.infradead.org
Cc: kernel@dh-electronics.com,
Alexander Stein <alexander.stein@ew.tq-group.com>,
Conor Dooley <conor+dt@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
Gregor Herburger <gregor.herburger@ew.tq-group.com>,
Hiago De Franco <hiago.franco@toradex.com>,
Hugo Villeneuve <hvilleneuve@dimonoff.com>,
Joao Paulo Goncalves <joao.goncalves@toradex.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Mathieu Othacehe <m.othacehe@gmail.com>,
Max Merchel <Max.Merchel@ew.tq-group.com>,
Michael Walle <mwalle@kernel.org>, Peng Fan <peng.fan@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Rob Herring <robh@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
devicetree@vger.kernel.org, imx@lists.linux.dev
Subject: Re: [PATCH 1/2] arm64: dts: imx8mp: Document DH i.MX8MP DHCOM SoM on DRC02 carrier board
Date: Wed, 25 Sep 2024 04:48:25 +0200 [thread overview]
Message-ID: <af9fe6ec-06fc-4ff8-8fcd-c2f9dfdfe5b0@denx.de> (raw)
In-Reply-To: <20240925001628.669604-1-marex@denx.de>
On 9/25/24 2:15 AM, Marek Vasut wrote:
> Document support for DH electronics i.MX8MP DHCOM SoM on DRC02 carrier board.
> This system is populated with two ethernet ports, two CANs, RS485 and RS232,
> USB, capacitive buttons and an OLED display.
Subject prefix should be dt-bindings: arm: fsl: , will be fixed in V2.
next prev parent reply other threads:[~2024-09-25 2:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 0:15 [PATCH 1/2] arm64: dts: imx8mp: Document DH i.MX8MP DHCOM SoM on DRC02 carrier board Marek Vasut
2024-09-25 0:15 ` [PATCH 2/2] arm64: dts: imx8mp: Add " Marek Vasut
2024-09-25 16:30 ` Frank Li
2024-09-25 21:09 ` Marek Vasut
2024-09-25 21:27 ` Frank Li
2024-09-25 22:08 ` Marek Vasut
2024-09-25 2:48 ` Marek Vasut [this message]
2024-09-25 14:36 ` [PATCH 1/2] arm64: dts: imx8mp: Document " Rob Herring (Arm)
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=af9fe6ec-06fc-4ff8-8fcd-c2f9dfdfe5b0@denx.de \
--to=marex@denx.de \
--cc=Max.Merchel@ew.tq-group.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=gregor.herburger@ew.tq-group.com \
--cc=hiago.franco@toradex.com \
--cc=hvilleneuve@dimonoff.com \
--cc=imx@lists.linux.dev \
--cc=joao.goncalves@toradex.com \
--cc=kernel@dh-electronics.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=m.othacehe@gmail.com \
--cc=mwalle@kernel.org \
--cc=peng.fan@nxp.com \
--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