From: Shawn Guo <shawnguo2@yeah.net>
To: Lukasz Majewski <lukma@denx.de>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Stefan Wahren <wahrenst@gmx.net>,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v11 2/3] dt-bindings: arm: Document the btt3 i.MX28 based board
Date: Mon, 17 Feb 2025 18:06:08 +0800 [thread overview]
Message-ID: <Z7MKEBkiBatFl54o@dragon> (raw)
In-Reply-To: <20241107085705.490940-2-lukma@denx.de>
On Thu, Nov 07, 2024 at 09:57:04AM +0100, Lukasz Majewski wrote:
> The imx287 based btt3 board is very similar to xea in terms of used SOM
> module.
>
> Signed-off-by: Lukasz Majewski <lukma@denx.de>
> Acked-by: Conor Dooley <conor.dooley@microchip.com>
Applied 2/3 and 3/3, thanks!
next prev parent reply other threads:[~2025-02-17 10:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 8:57 [PATCH v11 1/3] dt-bindings: display: Add powertip,{st7272|hx8238a} as DT Schema description Lukasz Majewski
2024-11-07 8:57 ` [PATCH v11 2/3] dt-bindings: arm: Document the btt3 i.MX28 based board Lukasz Majewski
2025-02-17 10:06 ` Shawn Guo [this message]
2024-11-07 8:57 ` [PATCH v11 3/3] ARM: dts: mxs: Add descriptions for imx287 based btt3-[012] devices Lukasz Majewski
2024-11-19 15:52 ` Lukasz Majewski
2024-12-09 8:46 ` Shawn Guo
2025-02-06 9:27 ` Lukasz Majewski
2025-02-12 8:52 ` Lukasz Majewski
2024-12-09 10:32 ` Stefan Wahren
2024-12-09 11:16 ` Lukasz Majewski
2024-12-09 9:52 ` [PATCH v11 1/3] dt-bindings: display: Add powertip,{st7272|hx8238a} as DT Schema description Lukasz Majewski
2024-12-20 10:29 ` Lukasz Majewski
2025-01-09 14:37 ` Lukasz Majewski
2025-01-09 15:12 ` Fabio Estevam
2025-01-09 15:32 ` Lukasz Majewski
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=Z7MKEBkiBatFl54o@dragon \
--to=shawnguo2@yeah.net \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--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=lukma@denx.de \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=wahrenst@gmx.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.