linux-kernel - Re: [PATCH 00/20] arm64: dts: qcom: Introduce Kaanapali platform device tree

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: <aTFPJwBq91r7o9Y2@duo.ucw.cz>
Date: Thu, 4 Dec 2025 10:06:47 +0100
From: Pavel Machek <pavel@....cz>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Jingyi Wang <jingyi.wang@....qualcomm.com>,
	Bjorn Andersson <andersson@...nel.org>,
	Konrad Dybcio <konradybcio@...nel.org>,
	Rob Herring <robh@...nel.org>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Conor Dooley <conor+dt@...nel.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,
	Tengfei Fan <tengfei.fan@....qualcomm.com>,
	Qiang Yu <qiang.yu@....qualcomm.com>,
	Manish Pandey <manish.pandey@....qualcomm.com>,
	Ronak Raheja <ronak.raheja@....qualcomm.com>,
	Jishnu Prakash <jishnu.prakash@....qualcomm.com>,
	Kamal Wadhwa <kamal.wadhwa@....qualcomm.com>,
	Jyothi Kumar Seerapu <jyothi.seerapu@....qualcomm.com>,
	Prasad Kumpatla <prasad.kumpatla@....qualcomm.com>,
	Hangxiang Ma <hangxiang.ma@....qualcomm.com>,
	Vikash Garodia <vikash.garodia@....qualcomm.com>
Subject: Re: [PATCH 00/20] arm64: dts: qcom: Introduce Kaanapali platform
 device tree

Hi!

> >>> Please cc phone-devel@...r.kernel.org with phone related patches.
> >>
> >> The cc list is generated by tools following the list in MAINTAINERS, you can get
> >> this series from devicetree@...r.kernel.org or linux-arm-msm@...r.kernel.org
> > 
> > Well, tools are not smart enough to generate good Cc list in this
> > case, so please do the cc manually. (I don't think they can be
> > improved easily, as it is not clear when code is phone-related from
> > the filename).
> 
> You cannot impose additional manual rules, just because you want

"You have to cc relevant list" is the rule that predates
automation. Just because automation does not work well in this case
does not mean you are exempt.

> Contributors for every standard patchset (there are only known 2
> exceptions for arm soc development and foo-devel is not one of them)
> must only use the tools and not cc phone-devel manually.

Untrue.
								Pavel

-- 
I don't work for Nazis and criminals, and neither should you.
Boycott Putin, Trump, Netanyahu and Musk!

Download attachment "signature.asc" of type "application/pgp-signature" (196 bytes)