From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Sumit Garg <sumit.garg@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Cc: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>,
Jens Wiklander <jens.wiklander@linaro.org>,
linux-arm-msm@vger.kernel.org, op-tee@lists.trustedfirmware.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] tee: qcomtee: call: Fix confusing cleanup.h syntax
Date: Mon, 15 Dec 2025 15:11:41 -0800 [thread overview]
Message-ID: <178f4564-8b59-4cf0-8274-dba7e58ba596@oss.qualcomm.com> (raw)
In-Reply-To: <aTtyR5J3AqXoE7to@sumit-X1>
On 12/11/2025 5:39 PM, Sumit Garg wrote:
> On Fri, Dec 12, 2025 at 02:07:40AM +0100, Krzysztof Kozlowski wrote:
>> Sure, fair. I just don't get why introducing cleanup.h without actually
>> accepting its explicitly documented style...
> TBH, it is likely overlooked during review of the QTEE driver. Having a
> builtin warning for the undesired syntax would help the reviewers here.
It is in the works:
https://patch.msgid.link/20251203-aheev-checkpatch-uninitialized-free-v7-1-841e3b31d8f3@gmail.com
next prev parent reply other threads:[~2025-12-15 23:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 2:08 [PATCH 1/3] tee: qcomtee: call: Fix confusing cleanup.h syntax Krzysztof Kozlowski
2025-12-08 2:08 ` [PATCH 2/3] tee: qcomtee: mem: " Krzysztof Kozlowski
2026-01-04 22:48 ` Amirreza Zarrabi
2025-12-08 2:08 ` [PATCH 3/3] tee: qcomtee: user: " Krzysztof Kozlowski
2026-01-04 22:50 ` Amirreza Zarrabi
2026-01-05 10:45 ` Jens Wiklander
2025-12-12 0:55 ` [PATCH 1/3] tee: qcomtee: call: " Sumit Garg
2025-12-12 1:07 ` Krzysztof Kozlowski
2025-12-12 1:39 ` Sumit Garg
2025-12-15 20:29 ` Amirreza Zarrabi
2025-12-16 7:33 ` Jens Wiklander
2026-01-04 21:42 ` Amirreza Zarrabi
2025-12-15 23:11 ` Jeff Johnson [this message]
2026-01-04 22:42 ` Amirreza Zarrabi
2026-01-05 10:44 ` Jens Wiklander
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=178f4564-8b59-4cf0-8274-dba7e58ba596@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=amirreza.zarrabi@oss.qualcomm.com \
--cc=jens.wiklander@linaro.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--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