From: Bjorn Andersson <andersson@kernel.org>
To: Maximilian Luz <luzmaximilian@gmail.com>,
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,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: Re: (subset) [PATCH v2 1/3] firmware: qcom: uefisecapp: Simplify mutex with guard
Date: Wed, 18 Mar 2026 08:50:09 -0500 [thread overview]
Message-ID: <177384182905.14526.16538779869751732076.b4-ty@kernel.org> (raw)
In-Reply-To: <20260216091525.107935-4-krzysztof.kozlowski@oss.qualcomm.com>
On Mon, 16 Feb 2026 10:15:26 +0100, Krzysztof Kozlowski wrote:
> Simplify error path unlocking mutex with the guard.
>
>
Applied, thanks!
[1/3] firmware: qcom: uefisecapp: Simplify mutex with guard
commit: 055d79affa436d83a6e0d3ca6d054f11a7e3d4c1
[2/3] firmware: qcom: uefisecapp: Annotate acquiring locks for context tracking
commit: 4bfb0ec11e20b9354beabf1b9f3e70e926c407bd
[3/3] firmware: qcom: scom: Simplify mutex with guard
commit: d98b978446d249df1a662b4fef4c0bbfa1d650b8
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2026-03-18 13:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 9:15 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
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 ` Bjorn Andersson [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=177384182905.14526.16538779869751732076.b4-ty@kernel.org \
--to=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®