From: Krzysztof Kozlowski <krzk@kernel.org>
To: Joseph Guo <qijian.guo@nxp.com>, Fabian Pflug <f.pflug@pengutronix.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, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
Haidong Zheng <haidong.zheng@nxp.com>,
Danwei Luo <danwei.luo@nxp.com>, Lei Xu <lei.xu@nxp.com>,
Justin Jiang <justin.jiang@nxp.com>
Subject: Re: [PATCH v3 2/2] arm64: dts: freescale: add support for NXP i.MX93 FRDM
Date: Mon, 10 Nov 2025 21:17:15 +0100 [thread overview]
Message-ID: <e00ba144-c5fc-47eb-8a9c-b6f33fa9704c@kernel.org> (raw)
In-Reply-To: <aRF9xlvWU/27+80K@lsvm11u0000395.swis.ap-northeast-2.aws.nxp.com>
On 10/11/2025 06:53, Joseph Guo wrote:
> On Wed, Oct 22, 2025 at 04:05:23PM +0200, Fabian Pflug wrote:
>> The FRDM i.MX 93 development board is a low-cost and compact development
>> board featuring the i.MX93 applications processor.
>>
>> It features:
>> - Dual Cortex-A55
>> - 2 GB LPDDR4X / LPDDR4
>> - 32 GB eMMC5.1
>> - MicroSD slot
>> - GbE RJ45 x 2
>> - USB2.0 1x Type C, 1x Type A
>>
>> This file is based upon the one provided by nxp in their own kernel and
>> yocto meta layer for the device, but adapted for mainline.
>>
>> Signed-off-by: Haidong Zheng <haidong.zheng@nxp.com>
>> Signed-off-by: Danwei Luo <danwei.luo@nxp.com>
>> Signed-off-by: Lei Xu <lei.xu@nxp.com>
>> Signed-off-by: Fabian Pflug <f.pflug@pengutronix.de>
> Hi Fabian,
>
> I'm maintainer of the NXP mainline for FRDM board.
No, you are not.
$ git grep 'Joseph Guo'
$ git grep qijian.guo@nxp.com
> Thanks for your contribution for FRDM board upstreaming.
> imx93 frdm board official name is FRDM-IMX93. Please change
> the name in commit message from FRDM i.MX 93 development board
> to FRDM-IMX93 board.
>
Huh? How does it matter? Why are you pointing such nits? This is not
helpful and consider that your naming in NXP does not matter.
Please kindly trim the replies from unnecessary context. It makes it
much easier to find new content.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-11-10 20:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 14:05 [PATCH v3 0/2] Add devicetree for NXP i.MX93 FRDM board Fabian Pflug
2025-10-22 14:05 ` [PATCH v3 1/2] dt-bindings: arm: fsl: add i.MX93 11x11 " Fabian Pflug
2025-10-22 14:05 ` [PATCH v3 2/2] arm64: dts: freescale: add support for NXP i.MX93 FRDM Fabian Pflug
2025-10-22 20:28 ` Francesco Valla
2025-11-10 5:31 ` Joseph Guo
2025-11-10 5:54 ` Joseph Guo
2025-11-10 5:53 ` Joseph Guo
2025-11-10 20:17 ` Krzysztof Kozlowski [this message]
2025-10-23 13:51 ` [PATCH v3 0/2] Add devicetree for NXP i.MX93 FRDM board 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=e00ba144-c5fc-47eb-8a9c-b6f33fa9704c@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=danwei.luo@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=f.pflug@pengutronix.de \
--cc=festevam@gmail.com \
--cc=haidong.zheng@nxp.com \
--cc=imx@lists.linux.dev \
--cc=justin.jiang@nxp.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=lei.xu@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qijian.guo@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;
as well as URLs for NNTP newsgroup(s).