From: Krzysztof Kozlowski <krzk@kernel.org>
To: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Harshal Dev <harshal.dev@oss.qualcomm.com>,
Konrad Dybcio <konradybcio@kernel.org>,
Sumit Garg <sumit.garg@kernel.org>,
Jens Wiklander <jens.wiklander@linaro.org>,
Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>,
Arnd Bergmann <arnd@arndb.de>,
Geert Uytterhoeven <geert+renesas@glider.be>,
op-tee@lists.trustedfirmware.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] arm64: defconfig: Enable QCOMTEE on Qualcomm SM8650+
Date: Wed, 10 Dec 2025 06:20:10 +0100 [thread overview]
Message-ID: <74a5319a-2801-4789-a3fe-fafaaa15cee1@kernel.org> (raw)
In-Reply-To: <CADLxj5S9qup2joSDLdrrVPgtzVcf6BXkz7TDEcnSQqSWUk8dtg@mail.gmail.com>
On 10/12/2025 04:51, Bjorn Andersson wrote:
> On Mon, Dec 8, 2025 at 10:14 PM Dmitry Baryshkov
> <dmitry.baryshkov@oss.qualcomm.com> wrote:
>> On Tue, 9 Dec 2025 at 07:58, Krzysztof Kozlowski <krzk@kernel.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@oss.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
next prev parent reply other threads:[~2025-12-10 5:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 12:18 Harshal Dev
2025-12-09 5:58 ` Krzysztof Kozlowski
2025-12-09 6:14 ` Dmitry Baryshkov
2025-12-10 3:51 ` Bjorn Andersson
2025-12-10 5:20 ` Krzysztof Kozlowski [this message]
2025-12-10 9:05 ` Harshal Dev
2025-12-12 1:25 ` Sumit Garg
2025-12-15 11:20 ` Harshal Dev
2025-12-22 16:56 ` Bjorn Andersson
2026-01-02 8:51 ` Harshal Dev
2026-01-02 18:23 ` Bjorn Andersson
2026-01-07 6:20 ` Harshal Dev
2026-01-07 15:04 ` Bjorn Andersson
2026-01-08 9:46 ` Harshal Dev
2025-12-09 7:15 ` Harshal Dev
2025-12-12 1:14 ` Sumit Garg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=74a5319a-2801-4789-a3fe-fafaaa15cee1@kernel.org \
--to=krzk@kernel.org \
--cc=amirreza.zarrabi@oss.qualcomm.com \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=geert+renesas@glider.be \
--cc=harshal.dev@oss.qualcomm.com \
--cc=jens.wiklander@linaro.org \
--cc=konradybcio@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=op-tee@lists.trustedfirmware.org \
--cc=sumit.garg@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®