The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Harshal Dev <harshal.dev@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
	Sumit Garg <sumit.garg@kernel.org>,
	Jens Wiklander <jens.wiklander@linaro.org>
Cc: 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] arm64: defconfig: Enable QCOMTEE for Qualcomm SoCs
Date: Fri, 5 Dec 2025 13:10:00 +0530	[thread overview]
Message-ID: <8c7cff73-fd42-4dfc-ad5b-265f8f09404f@oss.qualcomm.com> (raw)
In-Reply-To: <0196328a-86ef-48ef-9ea6-afbad520eb4f@kernel.org>

Hi, Krzysztof

On 12/2/2025 3:15 PM, Krzysztof Kozlowski wrote:
> On 02/12/2025 10:43, Krzysztof Kozlowski wrote:
>> On 02/12/2025 10:37, Harshal Dev wrote:
>>> Enable config for the QCOMTEE driver to facilitate communication with the
>>> Qualcomm Trusted Execution Environment (QTEE) on Qualcomm platforms.
>>
>> Which platforms use it?
>> Why this cannot be a module?
>>
> 
> Also, you did not really cc necessary lists. Use get_maintainers.pl on
> qcom soc code for example.

Sure, thanks for pointing this out, I will add the folks from Qcom SoC code in
the next patch. :)

Regards,
Harshal

> 
> 
> Best regards,
> Krzysztof


  reply	other threads:[~2025-12-05  7:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-02  9:37 [PATCH] arm64: defconfig: Enable QCOMTEE for Qualcomm SoCs Harshal Dev
2025-12-02  9:43 ` Krzysztof Kozlowski
2025-12-02  9:45   ` Krzysztof Kozlowski
2025-12-05  7:40     ` Harshal Dev [this message]
2025-12-05  7:38   ` Harshal Dev

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=8c7cff73-fd42-4dfc-ad5b-265f8f09404f@oss.qualcomm.com \
    --to=harshal.dev@oss.qualcomm.com \
    --cc=amirreza.zarrabi@oss.qualcomm.com \
    --cc=arnd@arndb.de \
    --cc=bjorn.andersson@oss.qualcomm.com \
    --cc=geert+renesas@glider.be \
    --cc=jens.wiklander@linaro.org \
    --cc=krzk@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