From: Sumit Garg <sumit.garg@kernel.org>
To: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>
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: Wed, 12 Nov 2025 13:17:46 +0530 [thread overview]
Message-ID: <aRQ7osB9rElutHuv@sumit-X1> (raw)
In-Reply-To: <2ec200e4-cf28-4881-837b-4455da047619@oss.qualcomm.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Sumit Garg via OP-TEE <op-tee@lists.trustedfirmware.org>
To: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>
Cc: 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: Wed, 12 Nov 2025 13:17:46 +0530 [thread overview]
Message-ID: <aRQ7osB9rElutHuv@sumit-X1> (raw)
In-Reply-To: <2ec200e4-cf28-4881-837b-4455da047619@oss.qualcomm.com>
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
next prev parent reply other threads:[~2025-11-12 7:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 21:28 [PATCH] tee: qcom: initialize result before use in release worker Amirreza Zarrabi
2025-11-10 21:28 ` Amirreza Zarrabi via OP-TEE
2025-11-11 6:48 ` Sumit Garg
2025-11-11 6:48 ` Sumit Garg via OP-TEE
2025-11-11 19:42 ` Amirreza Zarrabi
2025-11-11 19:42 ` Amirreza Zarrabi via OP-TEE
2025-11-12 7:47 ` Sumit Garg [this message]
2025-11-12 7:47 ` Sumit Garg via OP-TEE
2025-11-14 1:54 ` Amirreza Zarrabi
2025-11-14 1:54 ` Amirreza Zarrabi via OP-TEE
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=aRQ7osB9rElutHuv@sumit-X1 \
--to=sumit.garg@kernel.org \
--cc=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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.