From: Jarkko Nikula <jarkko.nikula@bitmer.com>
To: phucduc.bui@gmail.com, peter.ujfalusi@gmail.com, broonie@kernel.org
Cc: lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/7] ASoC: ti: Cleanup locking code using guard() helpers
Date: Sat, 9 May 2026 15:28:07 +0300 [thread overview]
Message-ID: <7249653a-84d6-47f4-8aa4-2cc734c42b8e@bitmer.com> (raw)
In-Reply-To: <20260508103837.138142-1-phucduc.bui@gmail.com>
On 08/05/2026 1:38 pm, phucduc.bui@gmail.com wrote:
> From: bui duc phuc <phucduc.bui@gmail.com>
>
> Hi all,
>
> This series converts mutex and spinlock handling in TI ASoC drivers
> to use guard() helpers.
>
> Most patches are straightforward conversions to guard() helpers.
> Two patches include minor cleanup changes in the process:
>
> omap-dmic: Simplified omap_dmic_dai_startup() by removing the
> temporary return variable and using a direct return path on error.
>
> omap-mcbsp: Modernized omap_mcbsp_request() by using __free(kfree)
> for memory management. This ensures that memory is always freed on
> error paths after the spinlock is released, without needing manual
> goto labels.
>
> No behavior change intended.
For this set + Tested-by tags for the patches 6 and 7:
Acked-by: Jarkko Nikula <jarkko.nikula@bitmer.com>
next prev parent reply other threads:[~2026-05-09 12:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 10:38 [PATCH 0/7] ASoC: ti: Cleanup locking code using guard() helpers phucduc.bui
2026-05-08 10:38 ` [PATCH 1/7] ASoC: ti: j721e-evm: Use guard() for mutex locks phucduc.bui
2026-05-08 10:38 ` [PATCH 2/7] ASoC: ti: omap-dmic: " phucduc.bui
2026-05-08 10:38 ` [PATCH 3/7] ASoC: ti: omap-hdmi: " phucduc.bui
2026-05-08 10:38 ` [PATCH 4/7] ASoC: ti: omap-mcpdm: " phucduc.bui
2026-05-08 10:38 ` [PATCH 5/7] ASoC: ti: ams-delta: Use guard() for spin locks phucduc.bui
2026-05-08 10:38 ` [PATCH 6/7] ASoC: ti: omap-mcbsp-st: " phucduc.bui
2026-05-09 12:26 ` Jarkko Nikula
2026-05-08 10:38 ` [PATCH 7/7] ASoC: ti: omap-mcbsp: Simplify lock and resource handling phucduc.bui
2026-05-10 1:35 ` Mark Brown
2026-05-11 4:44 ` Bui Duc Phuc
2026-05-13 3:14 ` Bui Duc Phuc
2026-05-14 1:35 ` Mark Brown
2026-05-14 10:35 ` Bui Duc Phuc
2026-05-09 12:28 ` Jarkko Nikula [this message]
2026-05-11 0:58 ` [PATCH 0/7] ASoC: ti: Cleanup locking code using guard() helpers Mark Brown
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=7249653a-84d6-47f4-8aa4-2cc734c42b8e@bitmer.com \
--to=jarkko.nikula@bitmer.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@gmail.com \
--cc=phucduc.bui@gmail.com \
--cc=tiwai@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.