linux-kernel - Re: [PATCH v2 3/4] dt-bindings: ufs: mediatek,ufs: add MT8195 compatible and update clock nodes

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: <4dc420a3-cf89-4f45-84e7-4d0079240681@kernel.org>
Date: Mon, 20 Oct 2025 11:56:36 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Peter Wang (王信友) <peter.wang@...iatek.com>,
 "chu.stanley@...il.com" <chu.stanley@...il.com>,
 "James.Bottomley@...senPartnership.com"
 <James.Bottomley@...senPartnership.com>, "robh@...nel.org"
 <robh@...nel.org>, "bvanassche@....org" <bvanassche@....org>,
 AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
 "linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
 "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
 Macpaul Lin (林智斌) <Macpaul.Lin@...iatek.com>,
 "conor+dt@...nel.org" <conor+dt@...nel.org>,
 "linux-mediatek@...ts.infradead.org" <linux-mediatek@...ts.infradead.org>,
 "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
 "krzk+dt@...nel.org" <krzk+dt@...nel.org>,
 "alim.akhtar@...sung.com" <alim.akhtar@...sung.com>,
 "linux-arm-kernel@...ts.infradead.org"
 <linux-arm-kernel@...ts.infradead.org>,
 "matthias.bgg@...il.com" <matthias.bgg@...il.com>,
 "avri.altman@....com" <avri.altman@....com>,
 "martin.petersen@...cle.com" <martin.petersen@...cle.com>
Cc: "macpaul@...il.com" <macpaul@...il.com>,
 Pablo Sun (孫毓翔) <pablo.sun@...iatek.com>,
 Project_Global_Chrome_Upstream_Group
 <Project_Global_Chrome_Upstream_Group@...iatek.com>,
 Bear Wang (萩原惟德) <bear.wang@...iatek.com>,
 Ramax Lo (羅明遠) <Ramax.Lo@...iatek.com>
Subject: Re: [PATCH v2 3/4] dt-bindings: ufs: mediatek,ufs: add MT8195
 compatible and update clock nodes

On 20/10/2025 11:44, Peter Wang (王信友) wrote:
> On Mon, 2025-10-20 at 10:28 +0200, Krzysztof Kozlowski wrote:
>>>
>>>
>>> Hi Krzysztof Kozlowski,
>>>
>>> The main reason for my objection was also clearly stated:
>>> "removing these DTS settings will make what was originally
>>> a simple task more complicated."
>>> I’m not sure if you are quoting only the "In addition"
>>> part to take it out of context?
>>
>> It is not out of context. It was the statement on its own.
> 
> Hi Krzysztof Kozlowski,
> 
> However, you haven’t addressed the main reason for my objection.
> "removing these DTS settings will make what was originally
> a simple task more complicated."


You did not object in technical matter at all here:
https://lore.kernel.org/all/ce0f9785f8f488010cd81adbbdb5ac07742fc988.camel@mediatek.com/

Look at this patch.

You said nothing about actual change, except blocking the community
maintainer. You did not raise any other concerns so what are you
speaking about "other main concerns"?

Even if such existed, they did not matter, because YOU WROTE ONLY:

"The role of MediaTek UFS maintainer is not suitable to be handed over
to someone outside of MediaTek."

This is what we discuss here.

> 
>>
>>
>>
>> You denied community to participate and now you twist the argument
>> like
>> you want Mediatek people to be involved. No one denied Mediatek to be
>> maintainer.
>>
>> It is you who denied community to join the maintainers.
>>
>> This is not acceptable and you still do not understand why.
> 
> I think I understand your point now, you believe that opposing
> this patch means opposing community participation and support, right?

Do you even read your own comments and where did you place them? Do you
understand that we discuss emails, not some unsaid or other threads?

Look at this:

https://lore.kernel.org/all/ce0f9785f8f488010cd81adbbdb5ac07742fc988.camel@mediatek.com/

	
> But it’s clear that you haven’t carefully considered the main 
> reason for my objection?

Main reason for objection? What?

> 
> 
> 
>>
>>
>> You could apologize and explain your mistakes, but instead you push
>> same
>> narrative.
>>
>> Still a red flag. I will not accept such vendor-like behaviors,
>> because
>> they significantly harm the community.
>>
>> I am very surprised that UFS maintainers did not object to it. This
>> should be clearly ostracized.
>>
>>
> 
> Sorry, I still don’t quite understand why having people who
> know the SoC better maintain the SoC driver would be considered
> harmful to the community?

You are twisting the problem, like anyone denied you being the maintainer.

YOU DENIED OTHER PEOPLE!

I finish the discussion here, I am considering your explanations
intentionally twisting the point thus I find it still harmful behavior.

Best regards,
Krzysztof