From: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>
To: Sumit Garg <sumit.garg@kernel.org>
Cc: Jens Wiklander <jens.wiklander@linaro.org>,
linux-arm-msm@vger.kernel.org, op-tee@lists.trustedfirmware.org,
linux-kernel@vger.kernel.org,
Dan Carpenter <dan.carpenter@linaro.org>
Subject: Re: [PATCH] tee: qcom: initialize result before use in release worker
Date: Fri, 14 Nov 2025 12:54:46 +1100 [thread overview]
Message-ID: <afba8148-b5a6-4f8e-a461-58cc62f37a7a@oss.qualcomm.com> (raw)
In-Reply-To: <aRQ7osB9rElutHuv@sumit-X1>
Hi Sumit,
On 11/12/2025 6:47 PM, Sumit Garg wrote:
> On Wed, Nov 12, 2025 at 06:42:04AM +1100, Amirreza Zarrabi wrote:
>> Hi Sumit,
>>
>> On 11/11/2025 5:48 PM, Sumit Garg wrote:
>>> On Mon, Nov 10, 2025 at 01:28:32PM -0800, Amirreza Zarrabi wrote:
>>>
>>> For the subject prefix lets try to follow the directory structure:
>>>
>>> tee: qcomtee: ...
>>>
>>
>> I believe we previously agreed on using tee: qcom: based on the reviewer’s
>> comments. Currently, there’s no commit message with qcomtee:.
>>
>> https://lore.kernel.org/op-tee/4rbfpubsaxgv2buksonfigbdkw6geas6l7pycxuukdymqfohga@ohd4hqzvra3w/
>>
>
> Yeah I agree I haven't been too picky about it earlier but lets follow a
> common practice which other TEEs also uses based on directory structure like:
>
> - tee: optee:
> - tee: amdtee:
> - tee: tstee:
> - tee: qcomtee:
>
> -Sumit
Sure. I'll update.
Regards,
Amir
prev parent reply other threads:[~2025-11-14 1:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 21:28 Amirreza Zarrabi
2025-11-11 6:48 ` Sumit Garg
2025-11-11 19:42 ` Amirreza Zarrabi
2025-11-12 7:47 ` Sumit Garg
2025-11-14 1:54 ` Amirreza Zarrabi [this message]
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=afba8148-b5a6-4f8e-a461-58cc62f37a7a@oss.qualcomm.com \
--to=amirreza.zarrabi@oss.qualcomm.com \
--cc=dan.carpenter@linaro.org \
--cc=jens.wiklander@linaro.org \
--cc=linux-arm-msm@vger.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®