From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: "Peter Wang (王信友)" <peter.wang@mediatek.com>,
"chu.stanley@gmail.com" <chu.stanley@gmail.com>,
"James.Bottomley@HansenPartnership.com"
<James.Bottomley@HansenPartnership.com>,
"robh@kernel.org" <robh@kernel.org>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Macpaul Lin (林智斌)" <Macpaul.Lin@mediatek.com>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"alim.akhtar@samsung.com" <alim.akhtar@samsung.com>,
"krzk@kernel.org" <krzk@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"avri.altman@wdc.com" <avri.altman@wdc.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "macpaul@gmail.com" <macpaul@gmail.com>,
"Pablo Sun (孫毓翔)" <pablo.sun@mediatek.com>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
"Bear Wang (萩原惟德)" <bear.wang@mediatek.com>,
"Ramax Lo (羅明遠)" <Ramax.Lo@mediatek.com>
Subject: Re: [PATCH v2 3/4] dt-bindings: ufs: mediatek,ufs: add MT8195 compatible and update clock nodes
Date: Mon, 20 Oct 2025 13:04:37 +0200 [thread overview]
Message-ID: <6de4477a-5c2e-413f-9aa2-77b7262ebb38@collabora.com> (raw)
In-Reply-To: <95d3fe686abcd4a6070c6613392fdb9605bdd73e.camel@mediatek.com>
Il 20/10/25 12:46, Peter Wang (王信友) ha scritto:
> On Mon, 2025-10-20 at 11:56 +0200, Krzysztof Kozlowski wrote:
>>
>> 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.
>>
>> 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?
>>
>
> Hi Krzysztof Kozlowski,
>
> I think you misunderstood—these are different patches.
> This one only changes the maintainer. What I was referring to
> is another patch that removes parts of the DTS setting.
> https://lore.kernel.org/all/eb47587159484abca8e6d65dddcf0844822ce99f.camel@mediatek.com/
>
>
> I don’t know who AngeloGioacchino is,
Sorry Peter, but a 10 seconds research on your side would have made you aware of
who I am.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/MAINTAINERS?h=v6.6#n2346
...then a 60 seconds research would reveal way more than just that about me,
and also your colleagues know me quite a bit :-)
Besides, you don't really need to know who somebody is to make an upstream review:
this is a community, and a good patch may come from old and recognized contributors
as much as from new ones sending their first patch upstream.
> so isn’t it reasonable for
> me to oppose directly changing the maintainer?
> Or do you think everyone should know who AngeloGioacchino is
> and just accept this change?
>
>
> Let’s put it this way: if a strager you don’t know suddenly comes
> to your home and says they’re now the maintainer of your house,
> would you be comfortable with that?
>
>
>
>>
>>
>> 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.
Krzysztof, many thanks for taking time to defend the community.
Regards,
Angelo
>>
>> Best regards,
>> Krzysztof
>
> I think you’re the one twisting my words.
> What I said was that I oppose people OUTSIDE of MediaTek becoming
> maintainers, not that I oppose other people in GENERAL.
> In fact, I also mentioned that other MediaTek maintainers
> would be joining.
>
>
> Thanks
> Peter
>
>
next prev parent reply other threads:[~2025-10-20 11:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 8:57 [PATCH v2 1/4] scsi: ufs: ufs-mediatek: Add UFS host support for MT8195 SoC Macpaul Lin
2025-07-22 8:57 ` [PATCH v2 2/4] dt-bindings: ufs: mediatek,ufs: add ufs-disable-mcq flag for UFS host Macpaul Lin
2025-07-23 4:45 ` Rob Herring (Arm)
2025-07-23 9:33 ` Peter Wang (王信友)
2025-07-22 8:57 ` [PATCH v2 3/4] dt-bindings: ufs: mediatek,ufs: add MT8195 compatible and update clock nodes Macpaul Lin
2025-07-22 9:39 ` AngeloGioacchino Del Regno
2025-07-23 4:50 ` Rob Herring
2025-07-23 7:33 ` Macpaul Lin (林智斌)
2025-07-23 8:10 ` AngeloGioacchino Del Regno
2025-07-23 9:41 ` Peter Wang (王信友)
2025-10-19 10:19 ` Krzysztof Kozlowski
2025-10-20 8:13 ` Peter Wang (王信友)
2025-10-20 8:28 ` Krzysztof Kozlowski
2025-10-20 9:44 ` Peter Wang (王信友)
2025-10-20 9:56 ` Krzysztof Kozlowski
2025-10-20 10:46 ` Peter Wang (王信友)
2025-10-20 11:04 ` AngeloGioacchino Del Regno [this message]
2025-10-20 11:46 ` Peter Wang (王信友)
2025-10-20 10:02 ` Krzysztof Kozlowski
2025-10-20 10:49 ` Peter Wang (王信友)
2025-07-22 8:57 ` [PATCH v2 4/4] arm64: dts: mediatek: mt8195: add UFSHCI node Macpaul Lin
2025-07-23 9:34 ` Peter Wang (王信友)
2025-07-23 9:33 ` [PATCH v2 1/4] scsi: ufs: ufs-mediatek: Add UFS host support for MT8195 SoC Peter Wang (王信友)
2025-07-31 4:44 ` Martin K. Petersen
2025-10-20 15:40 ` Bart Van Assche
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=6de4477a-5c2e-413f-9aa2-77b7262ebb38@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Macpaul.Lin@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=Ramax.Lo@mediatek.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=bear.wang@mediatek.com \
--cc=bvanassche@acm.org \
--cc=chu.stanley@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=macpaul@gmail.com \
--cc=martin.petersen@oracle.com \
--cc=matthias.bgg@gmail.com \
--cc=pablo.sun@mediatek.com \
--cc=peter.wang@mediatek.com \
--cc=robh@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