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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2fa188c3-f5c3-4145-9cae-3587f3bb23cc@kernel.org>
Date: Thu, 4 Dec 2025 11:41:11 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Pavel Machek <pavel@....cz>
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

On 04/12/2025 10:09, Pavel Machek wrote:
> On Wed 2025-12-03 19:41:59, Krzysztof Kozlowski wrote:
>> On 03/12/2025 19:40, Krzysztof Kozlowski wrote:
>>> On 03/12/2025 19:10, Pavel Machek wrote:
>>>> On Wed 2025-12-03 18:31:11, Krzysztof Kozlowski wrote:
>>>>> On 02/12/2025 19:21, Pavel Machek wrote:
>>>>>> Hi!
>>>>>>
>>>>>>> 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:
>>>>>>>
>>>>>>> - 1-3: MTP board boot-to-shell with basic function.
>>>>>>> - 4-16: More feature including PCIE, sdcard, usb, DSPs, PMIC related, tsense, bus, crypto etc. Add QRD board support.
>>>>>>> - 17-20: Multimedia features including audio, video and camss.
>>>>>>
>>>>>> Thanks for doing this. I assume there devices available with this are
>>>>>> quite expensive/hard to get at this point?
>>>>>>
>>>>>> Please cc phone-devel@...r.kernel.org with phone related patches.
>>>>>
>>>>> That's not even a phone, anyway contributors should not cc lists which
>>>>> are not relevant to the posting and not pointed out by maintainers. You
>>>>
>>>> People should Cc relevant lists, and yes, if it is called "Mobile Test
>>>> Platform", it is relevant to phone development.
>>
>> ... 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.

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

Then do not impose additional rules to cc foo-devel just because you
want the patches.

Best regards,
Krzysztof