imx.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Daniel Baluta <daniel.baluta@gmail.com>,
	Fabio Estevam <festevam@gmail.com>
Cc: Rogerio Pimentel <rpimentel.silva@gmail.com>,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	shawnguo@kernel.org, s.hauer@pengutronix.de,
	kernel@pengutronix.de, 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>,
	Daniel Baluta <daniel.baluta@nxp.com>,
	Joseph Guo <qijian.guo@nxp.com>
Subject: Re: [PATCH v4 2/2] arm64: dts: add support for NXP i.MX8MP FRDM board
Date: Wed, 12 Nov 2025 10:14:28 +0100	[thread overview]
Message-ID: <2e160fe1-bcb2-41cf-817e-ac2a36959b16@kernel.org> (raw)
In-Reply-To: <baafb460-fb65-4cd2-9911-89d828199d9b@kernel.org>

On 12/11/2025 10:08, Krzysztof Kozlowski wrote:
> On 12/11/2025 09:15, Daniel Baluta wrote:
>> On Tue, Nov 11, 2025 at 2:49 PM Daniel Baluta <daniel.baluta@gmail.com> wrote:
>>>
>>> On Tue, Nov 11, 2025 at 1:50 PM Fabio Estevam <festevam@gmail.com> wrote:
>>>>
>>>> Hi Daniel,
>>>>
>>>> On Tue, Nov 11, 2025 at 5:45 AM Daniel Baluta <daniel.baluta@gmail.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@nxp.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.
> 
> 


... and because last two months there were two or three cases where
vendor companies bullied individual contributors, I will be quite strict
about that. Vendor company does not receive any authorship on patches
sent by independent contributors which the vendor NEVER submitted,
unless author really wants that. But I will treat any such insisting on
authorship by vendor like NXP as bullying and working AGAINST the community.

Best regards,
Krzysztof

  reply	other threads:[~2025-11-12  9:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-09 21:45 [PATCH v4 1/2] dt-bindings: arm: fsl: Add i.MX8MP FRDM board Rogerio Pimentel
2025-11-09 21:45 ` [PATCH v4 2/2] arm64: dts: add support for NXP " Rogerio Pimentel
2025-11-10  5:15   ` Joseph Guo
2025-11-10 19:26     ` Fabio Estevam
2025-11-11 10:22       ` Daniel Baluta
2025-11-10 20:14     ` Krzysztof Kozlowski
2025-11-10 20:12   ` Krzysztof Kozlowski
2025-11-11  8:47     ` Daniel Baluta
2025-11-11 11:50       ` Fabio Estevam
2025-11-11 12:49         ` Daniel Baluta
2025-11-12  8:15           ` Daniel Baluta
2025-11-12  9:08             ` Krzysztof Kozlowski
2025-11-12  9:14               ` Krzysztof Kozlowski [this message]
2025-11-12  9:32                 ` Daniel Baluta
2025-11-12  9:40                   ` Krzysztof Kozlowski
2025-11-12 12:35                     ` Daniel Baluta
2025-11-12 14:04                       ` Rogerio Pimentel
2025-11-12 14:24                         ` Krzysztof Kozlowski
2025-11-10  1:04 ` [PATCH v4 1/2] dt-bindings: arm: fsl: Add " Rob Herring

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=2e160fe1-bcb2-41cf-817e-ac2a36959b16@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=daniel.baluta@gmail.com \
    --cc=daniel.baluta@nxp.com \
    --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=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=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;
as well as URLs for NNTP newsgroup(s).