public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Rogerio Pimentel <rpimentel.silva@gmail.com>,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	shawnguo@kernel.org, s.hauer@pengutronix.de
Cc: kernel@pengutronix.de, festevam@gmail.com,
	alexander.stein@ew.tq-group.com,
	dario.binacchi@amarulasolutions.com, marex@denx.de,
	Markus.Niebel@tq-group.com, y.moog@phytec.de,
	joao.goncalves@toradex.com, frieder.schrempf@kontron.de,
	josua@solid-run.com, francesco.dolcini@toradex.com,
	primoz.fiser@norik.com, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, Xiaofeng Wei <xiaofeng.wei@nxp.com>,
	Joseph Guo <qijian.guo@nxp.com>,
	Steven Yang <steven.yang@nxp.com>, Lei Xu <lei.xu@nxp.com>
Subject: Re: [PATCH v5 2/2] arm64: dts: add support for NXP i.MX8MP FRDM board
Date: Sun, 23 Nov 2025 11:23:12 +0100	[thread overview]
Message-ID: <b8d5e008-d004-4e4f-8229-1d8d23087718@kernel.org> (raw)
In-Reply-To: <7e50c694-af6b-40cc-b1dc-4dd4ecf85a8d@kernel.org>

On 23/11/2025 10:42, Krzysztof Kozlowski wrote:
> On 23/11/2025 01:36, Rogerio Pimentel wrote:
>> The FRDM-i.MX8MP is an NXP development platform based on the i.MX8M Plus
>> SoC, featuring a quad Cortex-A53, Cortex-M7 co-processor, 4GB LPDDR4,
>> 32GB eMMC, Wi-Fi 6/Bluetooth 5.4/802.15.4 tri-radio, Ethernet, HDMI/MIPI
>> display interfaces, camera connectors, and standard expansion headers.
>>
>> Based on the device tree found in the NXP repository at github
>> https://github.com/nxp-imx-support/meta-imx-frdm and on imx8mp-evk
>> board kernel mainline device tree.
>>
>> This is a basic device tree supporting:
>>
>>  - Quad Cortex-A53
>>  - 4GB LPDDR4 DRAM
>>  - PCA9450C PMIC with regulators
>>  - Two NXP PCAL6416 GPIO expanders
>>  - RGB LEDs via GPIO expander
>>  - I2C1, I2C2, I2C3 controllers
>>  - UART2 (console) and UART3 (with RTS/CTS)
>>  - USDHC3 (8-bit eMMC)
>>  - SNVS power key (onboard power button)
>>
>> Author: Xiaofeng Wei <xiaofeng.wei@nxp.com>
> 
> There is no such tag. Use git commit --amend --reset-author to set the
> author.
> 
>> Signed-off-by: Xiaofeng Wei <xiaofeng.wei@nxp.com>
>>
>> Co-developed-by: Joseph Guo <qijian.guo@nxp.com>
>> Signed-off-by: Joseph Guo <qijian.guo@nxp.com>
>>
> 
> There is never blank line between tags.
> 
>> Co-developed-by: Steven Yang <steven.yang@nxp.com>
>> Signed-off-by: Steven Yang <steven.yang@nxp.com>
>>
>> Co-developed-by: Lei Xu <lei.xu@nxp.com>
>> Signed-off-by: Lei Xu <lei.xu@nxp.com>
>>
>> Co-developed-by: Rogerio Pimentel <rpimentel.silva@gmail.com>
>> Signed-off-by: Rogerio Pimentel <rpimentel.silva@gmail.com>
>> ---
>>
>> Changes in v5:
>>
>>  - Replace underscores (_) in node names with dashes (-)
>>  - Added missing Co-developed-by and Signed-off-by tags from all contributors
> 
> I assume you actually saw these SoBs in the code you took as your base?
> Remember, do not add SoBs which were never present in the original work
> (if company asks you, you can politely reply that they need to read what
> SoB means)
> 
> That's anyway weirdly a lot of co-developed tags, are you sure they
> wrote the code you took as the base here?

Although I think you mentioned you wanted all these last time, so it's
fine. Although I did not think you will literally use that syntax and
literally all the tags from Daniel's responses, because the syntax was
not correct.

Best regards,
Krzysztof

      reply	other threads:[~2025-11-23 10:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-23  0:36 [PATCH v5 1/2] dt-bindings: arm: fsl: Add i.MX8MP FRDM board Rogerio Pimentel
2025-11-23  0:36 ` [PATCH v5 2/2] arm64: dts: add support for NXP " Rogerio Pimentel
2025-11-23  9:42   ` Krzysztof Kozlowski
2025-11-23 10:23     ` Krzysztof Kozlowski [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=b8d5e008-d004-4e4f-8229-1d8d23087718@kernel.org \
    --to=krzk@kernel.org \
    --cc=Markus.Niebel@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@gmail.com \
    --cc=francesco.dolcini@toradex.com \
    --cc=frieder.schrempf@kontron.de \
    --cc=imx@lists.linux.dev \
    --cc=joao.goncalves@toradex.com \
    --cc=josua@solid-run.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=marex@denx.de \
    --cc=primoz.fiser@norik.com \
    --cc=qijian.guo@nxp.com \
    --cc=robh@kernel.org \
    --cc=rpimentel.silva@gmail.com \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=steven.yang@nxp.com \
    --cc=xiaofeng.wei@nxp.com \
    --cc=y.moog@phytec.de \
    /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