Re: [PATCH v2 00/11] ASoC: fsl: Use guard() for mutex & spin locks
From: Mark Brown <broonie@kernel.org>
Date: 2026-06-30 11:16:39
Also in:
imx, linux-arm-kernel, linux-sound, lkml
On Mon, 15 Jun 2026 16:38:13 +0700, phucduc.bui@gmail.com wrote:
ASoC: fsl: Use guard() for mutex & spin locks From: bui duc phuc <redacted> Hi all, This series converts mutex and spinlock handling in the FSL sound drivers to use guard() helpers. The changes are code cleanup only and should have no functional impact. [...]
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-7.3 Thanks! [01/11] ASoC: fsl_asrc: Use guard() for spin locks https://git.kernel.org/broonie/sound/c/d7e261b7ad1b [02/11] ASoC: fsl_audmix: Use guard() for spin locks https://git.kernel.org/broonie/sound/c/58712476dee2 [03/11] ASoC: fsl_easrc: Use guard() for spin locks https://git.kernel.org/broonie/sound/c/48d84310be60 [04/11] ASoC: fsl_esai: Use guard() for spin locks https://git.kernel.org/broonie/sound/c/cb87bdabd341 [05/11] ASoC: fsl_spdif: Use guard() for spin locks https://git.kernel.org/broonie/sound/c/a1b865cff274 [06/11] ASoC: fsl_ssi: Use guard() for mutex locks https://git.kernel.org/broonie/sound/c/4d748e7082ec [07/11] ASoC: fsl_xcvr: Use guard() for spin locks https://git.kernel.org/broonie/sound/c/94b0cb1dd6d9 [08/11] ASoC: imx-audio-rpmsg: Use guard() for spin locks https://git.kernel.org/broonie/sound/c/929d412fdb0d [09/11] ASoC: fsl_rpmsg: Use guard() for mutex & spin locks https://git.kernel.org/broonie/sound/c/11ce4dd4e7be [10/11] ASoC: fsl: mpc5200_dma: Use guard() for spin locks https://git.kernel.org/broonie/sound/c/caed9fb2e428 [11/11] ASoC: fsl: mpc5200_psc_ac97: Use guard() for mutex locks https://git.kernel.org/broonie/sound/c/8a2d7e46317a All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark