From: Krzysztof Kozlowski <krzk@kernel.org>
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>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"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>,
"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 12:02:29 +0200 [thread overview]
Message-ID: <3f5e2d98-4c4a-4a8b-b041-200bb1fc3e7e@kernel.org> (raw)
In-Reply-To: <4b3d2678d2b724fb53ec7272ef8daf52197d4a0e.camel@mediatek.com>
On 20/10/2025 11:44, Peter Wang (王信友) wrote:
>>
>> Consider stepping down and choosing them if they better understand
>> how
>> upstream works.
>>
>> As Rob wrote earlier:
>>
>> "Sounds like we need a new maintainer then. They clearly don't
>> understand that downstream doesn't exist."
>>
>>
>> Best regards,
>> Krzysztof
>
> I must reiterate that I do not oppose patches that are
> beneficial to the community; I only object to patches that are
> not helpful.
Let's quote you again:
"*In addition*, it will require MediaTek to put in extra
effort to migrate the kernel. "
This is ADDITIONAL argument you used. This is what you wrote, this is
what you claimed to be ADDITIONAL argument.
In your opinion ADDITIONAL argument is downstream and you still do not
understand why such argument is instant NAK for you as reviewer.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-20 10:02 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
2025-10-20 11:46 ` Peter Wang (王信友)
2025-10-20 10:02 ` Krzysztof Kozlowski [this message]
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=3f5e2d98-4c4a-4a8b-b041-200bb1fc3e7e@kernel.org \
--to=krzk@kernel.org \
--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=angelogioacchino.delregno@collabora.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=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