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: <74a5319a-2801-4789-a3fe-fafaaa15cee1@kernel.org>
Date: Wed, 10 Dec 2025 06:20:10 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Bjorn Andersson <bjorn.andersson@....qualcomm.com>,
 Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
Cc: Harshal Dev <harshal.dev@....qualcomm.com>,
 Konrad Dybcio <konradybcio@...nel.org>, Sumit Garg <sumit.garg@...nel.org>,
 Jens Wiklander <jens.wiklander@...aro.org>,
 Amirreza Zarrabi <amirreza.zarrabi@....qualcomm.com>,
 Arnd Bergmann <arnd@...db.de>, Geert Uytterhoeven <geert+renesas@...der.be>,
 op-tee@...ts.trustedfirmware.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] arm64: defconfig: Enable QCOMTEE on Qualcomm SM8650+

On 10/12/2025 04:51, Bjorn Andersson wrote:
> On Mon, Dec 8, 2025 at 10:14 PM Dmitry Baryshkov
> <dmitry.baryshkov@....qualcomm.com> wrote:
>> On Tue, 9 Dec 2025 at 07:58, Krzysztof Kozlowski <krzk@...nel.org> wrote:
>>>
>>> On 08/12/2025 13:18, Harshal Dev wrote:
>>>> Enable QCOMTEE driver on Qualcomm SM8650+ SoCs to facilitate communication
>>>> with the Qualcomm Trusted Execution Environment (QTEE).
>>>> (No enablement required in DTS files since QCOMTEE device is dynamically
>>>> registered by the QCOM_SCM firmware driver)
>>>>
>>>> Signed-off-by: Harshal Dev <harshal.dev@....qualcomm.com>
>>>> ---
>>>> Changes in v3:
>>>> - Updated the commit message to reflect the supported Qualcomm platforms.
>>>> - Link to v2: https://lore.kernel.org/r/20251205-qcom_qcomtee_defconfig-v2-1-c92560b0346e@qti.qualcomm.com
>>>>
>>>
>>> I gave you the exact example to follow. Maybe it is not that important
>>> for others, so I will not object, but OTOH it is important for me, thus
>>> I will not give reviewed by. I damn asked VERY CLEARLY:
>>>
>>> "Just mention which UPSTREAM boards (which you called Qualcomm
>>> platforms) use this driver."
>>
>> +1 Here. Defconfig changes mention devices, not SoC families.
>>
> 
> I don't agree that you have to mention a specific board, if the
> feature is used by all boards. But I think the commit message should
> make _that_ clear.


Yes, that would be enough and I would be fine with it as well, but I did
not have that impression from the commit msg.


Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ