linux-kernel - Re: [PATCH v4 2/2] arm64: dts: add support for NXP i.MX8MP FRDM board

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <baafb460-fb65-4cd2-9911-89d828199d9b@kernel.org>
Date: Wed, 12 Nov 2025 10:08:29 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Daniel Baluta <daniel.baluta@...il.com>,
 Fabio Estevam <festevam@...il.com>
Cc: Rogerio Pimentel <rpimentel.silva@...il.com>, robh@...nel.org,
 krzk+dt@...nel.org, conor+dt@...nel.org, shawnguo@...nel.org,
 s.hauer@...gutronix.de, kernel@...gutronix.de,
 alexander.stein@...tq-group.com, dario.binacchi@...rulasolutions.com,
 marex@...x.de, Markus.Niebel@...group.com, y.moog@...tec.de,
 joao.goncalves@...adex.com, frieder.schrempf@...tron.de,
 josua@...id-run.com, francesco.dolcini@...adex.com, primoz.fiser@...ik.com,
 imx@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org,
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
 Xiaofeng Wei <xiaofeng.wei@....com>, Daniel Baluta <daniel.baluta@....com>,
 Joseph Guo <qijian.guo@....com>
Subject: Re: [PATCH v4 2/2] arm64: dts: add support for NXP i.MX8MP FRDM board

On 12/11/2025 09:15, Daniel Baluta wrote:
> On Tue, Nov 11, 2025 at 2:49 PM Daniel Baluta <daniel.baluta@...il.com> wrote:
>>
>> On Tue, Nov 11, 2025 at 1:50 PM Fabio Estevam <festevam@...il.com> wrote:
>>>
>>> Hi Daniel,
>>>
>>> On Tue, Nov 11, 2025 at 5:45 AM Daniel Baluta <daniel.baluta@...il.com> wrote:
>>>
>>>> In addition to that, Rogerio please read:
>>>>
>>>> https://docs.kernel.org/process/submitting-patches.html
>>>>
>>>> At this moment I think you should keep the original author of the
>>>> patch.
>>>
>>> Right, but NXP makes a total mess with authorship.
>>
>> I cannot disagree with you on this, let me clarify it internally with
>> NXP colleagues
>> and sort everything out.
> 
> Hi Fabio & Rogerio,
> 
> Checked internally and to track the correct authorship and development work
> here is how NXP would prefer to get credit.

Sorry, but individual contributors do not need to give any credits to
NXP. If NXP wanted to sent the patches to have credit, they would do it.

Did sending happened?

If not, then any contributor is rightful to take the patches from
downstream and send them only, ONLY with their authorship. That's what
DCO allows and that's what established practice as well.

NXP had a chance to upstream. When they decided not to, they forfeit any
rights to claim they want any authorship.


> 
> #Use git commit --amend --author="Xiaofeng Wei <xiaofeng.wei@....com>"

NAK, there is no single patch like that from above author:

https://lore.kernel.org/all/?q=f%3Axiaofeng.wei%40nxp.com

Remember, downstream code does not matter. Does not exist.


> Author: Xiaofeng Wei <xiaofeng.wei@....com>
> 
> Signed-off-by: Xiaofeng Wei <xiaofeng.wei@....com>
> 
> Co-developed-by: Joseph Guo <qijian.guo@....com>
> Signed-off-by: Joseph Guo <qijian.guo@....com>
> 
> Co-developed-by: Steven Yang <steven.yang@....com>
> Signed-off-by: Steven Yang <steven.yang@....com>
> 
> Co-developed-by: Lei Xu <lei.xu@....com>
> Signed-off-by: Lei Xu <lei.xu@....com>
> 
> Then you can add your own C-d-b and S-o-b.
> 
> Thanks,
> Daniel.


Best regards,
Krzysztof