linux-kernel - Re: [PATCH] dt-bindings: thermal: qcom-tsens: document the Kaanapali Temperature Sensor

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] [day] [month] [year] [list]

Message-ID: <c15b7ee3-cae0-4cbf-8ea6-4d2b6ebee9de@kernel.org>
Date: Thu, 9 Oct 2025 20:03:21 +0900
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Jingyi Wang <jingyi.wang@....qualcomm.com>,
 Amit Kucheria <amitk@...nel.org>, Thara Gopinath <thara.gopinath@...il.com>,
 "Rafael J. Wysocki" <rafael@...nel.org>,
 Daniel Lezcano <daniel.lezcano@...aro.org>, Zhang Rui <rui.zhang@...el.com>,
 Lukasz Luba <lukasz.luba@....com>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>
Cc: linux-pm@...r.kernel.org, linux-arm-msm@...r.kernel.org,
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
 aiqun.yu@....qualcomm.com, tingwei.zhang@....qualcomm.com,
 trilok.soni@....qualcomm.com, yijie.yang@....qualcomm.com,
 Manaf Meethalavalappu Pallikunhi <manaf.pallikunhi@....qualcomm.com>
Subject: Re: [PATCH] dt-bindings: thermal: qcom-tsens: document the Kaanapali
 Temperature Sensor

On 25/09/2025 08:37, Jingyi Wang wrote:
> From: Manaf Meethalavalappu Pallikunhi <manaf.pallikunhi@....qualcomm.com>
> 
> Document the Temperature Sensor (TSENS) on the Kaanapali Platform.
> 
> Signed-off-by: Manaf Meethalavalappu Pallikunhi <manaf.pallikunhi@....qualcomm.com>
> Signed-off-by: Jingyi Wang <jingyi.wang@....qualcomm.com>
> ---

No, conflicting patch with Kaanapali, without any reason. Squash the
patches.

This entire split is just huge churn, huge duplication of work and quite
a lot of review put onto the community. You should have coordinated your
work better.

I am disappointed because you just don't think about the reviewing
process, about what maintainers should do with that. You just send what
was told you to send.

Explain to us - why do we want to have two 99% same patches sent the
SAME DAY, from the same company, sent in completely separate patchsets
so any simplified review will not be possible, and do same work - review
and applying - twice, instead of having only one?

Why maintainers should accept this?

Best regards,
Krzysztof