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

Krzysztof Kozlowski
2025-12-04T09:01:42Z

On 04/12/2025 09:56, Pavel Machek wrote:
> On Thu 2025-12-04 10:41:53, Jingyi Wang wrote:
>>
>>
>> On 12/3/2025 2:21 AM, 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@vger.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@vger.kernel.org or linux-arm-msm@vger.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 your
list to be cc-ed. If you want that list to be cc-ed, you need to improve
the tools, not use excuse they are not good enough and push this task to
contributors.

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.

Best regards,
Krzysztof