From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
Maximilian Luz <luzmaximilian@gmail.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH v2 2/3] firmware: qcom: uefisecapp: Annotate acquiring locks for context tracking
Date: Mon, 16 Feb 2026 12:11:04 +0100 [thread overview]
Message-ID: <f18d6c73-c701-4ca2-b017-7020559d547c@oss.qualcomm.com> (raw)
In-Reply-To: <20260216091525.107935-5-krzysztof.kozlowski@oss.qualcomm.com>
On 2/16/26 10:15 AM, Krzysztof Kozlowski wrote:
> qcuefi_acquire() and qcuefi_release() end with mutex locked or unlocked
> respectively, so annotate them so the lock usage will be tracked by
> context tracking tools.
>
> Note that mutex is tracked since commit 370f0a345a70 ("locking/mutex:
> Support Clang's context analysis").
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
>
> ---
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
next prev parent reply other threads:[~2026-02-16 11:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 9:15 [PATCH v2 1/3] firmware: qcom: uefisecapp: Simplify mutex with guard Krzysztof Kozlowski
2026-02-16 9:15 ` [PATCH v2 2/3] firmware: qcom: uefisecapp: Annotate acquiring locks for context tracking Krzysztof Kozlowski
2026-02-16 11:11 ` Konrad Dybcio [this message]
2026-02-16 9:15 ` [PATCH v2 3/3] firmware: qcom: scom: Simplify mutex with guard Krzysztof Kozlowski
2026-02-16 11:11 ` Konrad Dybcio
2026-02-16 11:10 ` [PATCH v2 1/3] firmware: qcom: uefisecapp: " Konrad Dybcio
2026-03-18 13:50 ` (subset) " Bjorn Andersson
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=f18d6c73-c701-4ca2-b017-7020559d547c@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=justinstitt@google.com \
--cc=konradybcio@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=luzmaximilian@gmail.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
/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®