From: Conor Dooley <conor@kernel.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: linux-kernel@vger.kernel.org,
Matteo Lisi <matteo.lisi@engicam.com>,
linux-amarula@amarulasolutions.com,
Alexander Stein <alexander.stein@ew.tq-group.com>,
Conor Dooley <conor+dt@kernel.org>,
Fabio Estevam <festevam@denx.de>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
Frieder Schrempf <frieder.schrempf@kontron.de>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Marek Vasut <marex@denx.de>,
Markus Niebel <Markus.Niebel@tq-group.com>,
Max Merchel <Max.Merchel@ew.tq-group.com>,
Michael Walle <mwalle@kernel.org>, Peng Fan <peng.fan@nxp.com>,
Rob Herring <robh@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
Tim Harvey <tharvey@gateworks.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 01/10] dt-bindings: arm: fsl: support Engicam MicroGEA BMM board
Date: Mon, 9 Jun 2025 17:46:46 +0100 [thread overview]
Message-ID: <20250609-lustrous-transform-63168641988e@spud> (raw)
In-Reply-To: <20250607093342.2248695-2-dario.binacchi@amarulasolutions.com>
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
On Sat, Jun 07, 2025 at 11:33:13AM +0200, Dario Binacchi wrote:
> Add devicetree bindings for Engicam MicroGEA BMM board based on the
> Engicam MicroGEA SoM (System-on-Module).
>
> The use of an enum for a single element is justified by the future
> addition of other boards based on the same SoM.
>
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-06-09 16:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-07 9:33 [PATCH 00/10] Support Engicam MicroGEA boards Dario Binacchi
2025-06-07 9:33 ` [PATCH 01/10] dt-bindings: arm: fsl: support Engicam MicroGEA BMM board Dario Binacchi
2025-06-09 16:46 ` Conor Dooley [this message]
2025-06-07 9:33 ` [PATCH 02/10] ARM: dts: imx6ul: support Engicam MicroGEA-MX6UL SoM Dario Binacchi
2025-06-07 14:02 ` Andrew Lunn
2025-06-07 9:33 ` [PATCH 03/10] ARM: dts: imx6ul: support Engicam MicroGEA BMM board Dario Binacchi
2025-06-09 9:38 ` Peng Fan
2025-06-07 9:33 ` [PATCH 06/10] dt-bindings: arm: fsl: support Engicam MicroGEA RMM board Dario Binacchi
2025-06-09 16:47 ` Conor Dooley
2025-06-07 9:33 ` [PATCH 07/10] ARM: dts: imx6ul: " Dario Binacchi
2025-06-09 9:41 ` Peng Fan
2025-06-07 9:33 ` [PATCH 08/10] dt-bindings: arm: fsl: support Engicam MicroGEA GTW board Dario Binacchi
2025-06-09 16:47 ` Conor Dooley
2025-06-07 9:33 ` [PATCH 09/10] ARM: dts: imx6ul: " Dario Binacchi
2025-06-09 9:43 ` Peng Fan
2025-06-09 9:45 ` [PATCH 00/10] Support Engicam MicroGEA boards Peng Fan
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=20250609-lustrous-transform-63168641988e@spud \
--to=conor@kernel.org \
--cc=Markus.Niebel@tq-group.com \
--cc=Max.Merchel@ew.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@denx.de \
--cc=francesco.dolcini@toradex.com \
--cc=frieder.schrempf@kontron.de \
--cc=krzk+dt@kernel.org \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=matteo.lisi@engicam.com \
--cc=mwalle@kernel.org \
--cc=peng.fan@nxp.com \
--cc=robh@kernel.org \
--cc=shawnguo@kernel.org \
--cc=tharvey@gateworks.com \
/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