linux-kernel - Re: [PATCH] tee: qcom: initialize result before use in release worker

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: <aRQ7osB9rElutHuv@sumit-X1>
Date: Wed, 12 Nov 2025 13:17:46 +0530
From: Sumit Garg <sumit.garg@...nel.org>
To: Amirreza Zarrabi <amirreza.zarrabi@....qualcomm.com>
Cc: Jens Wiklander <jens.wiklander@...aro.org>,
	linux-arm-msm@...r.kernel.org, op-tee@...ts.trustedfirmware.org,
	linux-kernel@...r.kernel.org,
	Dan Carpenter <dan.carpenter@...aro.org>
Subject: Re: [PATCH] tee: qcom: initialize result before use in release worker

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