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: <aTFzmm3fyxC1MAzk@duo.ucw.cz>
Date: Thu, 4 Dec 2025 12:42:18 +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

> >>>>>>> Introduce the Device Tree for the recently announced Snapdragon SoC from Qualcomm:
> >>>>>>> https://www.qualcomm.com/products/mobile/snapdragon/smartphones/snapdragon-8-series-mobile-platforms/snapdragon-8-elite-gen-5

> >>>>>>> Bindings and base Device Tree for the Kaanapali SoC, MTP (Mobile Test Platform)
> >>>>>>> and QRD (Qualcommm Reference Device) are splited in three:

> >> ... and btw, I know what MTP and QRD is and MTP IS NOT A PHONE. I work
> >> on this, I upstream this and it is not a phone, regardless how you call
> >> it. Just because we call our evalkit like that, does not make it a
> > phone.
> > 
> > So what is it?
> 
> evalkit for SoC. Just like every other NXP evalkit board is.

...products/mobile/snapdragon/smartphones/snapdragon-8-series-mobile-platforms...
...Mobile Test Platform...

Clearly not phone related.

> >>> new-hardware-devel or whatever. No. People should use tools, not guess
> >>> the cc lists. Fix the tools if you miss any Cc.

Where did you get that "people should completely rely on tools" thing from?

"You should always copy the appropriate subsystem maintainer(s) on any patch
to code that they maintain; look through the MAINTAINERS file and the
source code revision history to see who those maintainers are.  The
script scripts/get_maintainer.pl can be very useful at this step (pass paths to
your patches as arguments to scripts/get_maintainer.pl).  If you cannot find a
maintainer for the subsystem you are working on, Andrew Morton
(akpm@...ux-foundation.org) serves as a maintainer of last resort.

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.  Look in the MAINTAINERS file for a
subsystem-specific list; your patch will probably get more attention there.
Please do not spam unrelated lists, though.

Many kernel-related lists are hosted on vger.kernel.org; you can find a
list of them at http://vger.kernel.org/vger-lists.html.  There are
kernel-related lists hosted elsewhere as well, though."

									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)