From: wangdich9700@163.com
To: perex@perex.cz, tiwai@suse.com, wangdich9700@163.com,
wangdicheng@kylinos.cn
Cc: david.rhodes@cirrus.com, patches@opensource.cirrus.com,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] ALSA: hda: Use scoped_guard() for remaining manual mutex handling
Date: Wed, 1 Jul 2026 14:51:05 +0800 [thread overview]
Message-ID: <20260701065108.596046-1-wangdich9700@163.com> (raw)
From: wangdicheng <wangdicheng@kylinos.cn>
Replace the remaining manual mutex_lock/mutex_unlock pairs in the
HD-Audio subsystem with scoped_guard(), which provides automatic
lock release through RAII-style scope management.
No functional changes in any patch.
wangdicheng (3):
ALSA: hda/cs35l41: Use scoped_guard() for fw_mutex in
cs35l41_hda_bind()
ALSA: hda/cs35l56: Use scoped_guard() for irq_lock in
cs35l56_hda_fw_load()
ALSA: hda: Use scoped_guard() for open_mutex in azx_pcm_open()
sound/hda/codecs/side-codecs/cs35l41_hda.c | 57 ++++----
sound/hda/codecs/side-codecs/cs35l56_hda.c | 104 +++++++-------
sound/hda/common/controller.c | 159 +++++++++++----------
3 files changed, 161 insertions(+), 159 deletions(-)
--
2.25.1
next reply other threads:[~2026-07-01 6:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 6:51 wangdich9700 [this message]
2026-07-01 6:51 ` [PATCH 1/3] ALSA: hda/cs35l41: Use scoped_guard() for fw_mutex in cs35l41_hda_bind() wangdich9700
2026-07-01 6:51 ` [PATCH 2/3] ALSA: hda/cs35l56: Use scoped_guard() for irq_lock in cs35l56_hda_fw_load() wangdich9700
2026-07-01 9:46 ` Richard Fitzgerald
2026-07-01 10:03 ` Takashi Iwai
2026-07-01 6:51 ` [PATCH 3/3] ALSA: hda: Use scoped_guard() for open_mutex in azx_pcm_open() wangdich9700
-- strict thread matches above, loose matches on Subject: below --
2026-07-01 6:49 [PATCH 0/3] ALSA: hda: Use scoped_guard() for remaining manual mutex handling wangdich9700
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=20260701065108.596046-1-wangdich9700@163.com \
--to=wangdich9700@163.com \
--cc=david.rhodes@cirrus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=wangdicheng@kylinos.cn \
/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®