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: <aTF0KKFq0Ibyymz+@duo.ucw.cz>
Date: Thu, 4 Dec 2025 12:44:40 +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!

> No, there is no rule of Cc-ing phone-devel. No one has to do it and you
> need to stop coming with the impression that it is sanctioned rule by
> any platform or architecture maintainer.

Yes, people need to cc relevant mailing lists, that's why we have the
lists, and that's how kernel development works. You want relevant
developers, well, to review the patch.

"You should also normally choose at least one mailing list to receive a copy
of your patch set.  linux-kernel@...r.kernel.org should be used by default
for all patches, but the volume on that list has caused a number of
developers to tune it out."
							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)