[PATCH 0/2] ASoC: sti: Use guard() for mutex & spin locks

phucduc.bui@gmail.com posted 2 patches 1 week, 5 days ago
sound/soc/sti/uniperif_player.c | 73 ++++++++++++++-------------------
sound/soc/sti/uniperif_reader.c | 20 ++++-----
2 files changed, 38 insertions(+), 55 deletions(-)
[PATCH 0/2] ASoC: sti: Use guard() for mutex & spin locks
Posted by phucduc.bui@gmail.com 1 week, 5 days ago
From: bui duc phuc <phucduc.bui@gmail.com>

Hi all,

This series converts mutex and spinlock handling in the STI drivers
to use guard() helpers.
The changes are code cleanup only and should have no functional impact.
Compile tested only.

Best regards,
Phuc

bui duc phuc (2):
  ASoC: sti: uniperif_reader: Use guard() for spin locks
  ASoC: sti: uniperif_player: Use guard() for mutex & spin locks

 sound/soc/sti/uniperif_player.c | 73 ++++++++++++++-------------------
 sound/soc/sti/uniperif_reader.c | 20 ++++-----
 2 files changed, 38 insertions(+), 55 deletions(-)

-- 
2.43.0
Re: [PATCH 0/2] ASoC: sti: Use guard() for mutex & spin locks
Posted by Mark Brown 1 week ago
On Wed, 27 May 2026 17:02:04 +0700, phucduc.bui@gmail.com wrote:
> ASoC: sti: Use guard() for mutex & spin locks
> 
> From: bui duc phuc <phucduc.bui@gmail.com>
> 
> Hi all,
> 
> This series converts mutex and spinlock handling in the STI drivers
> to use guard() helpers.
> The changes are code cleanup only and should have no functional impact.
> Compile tested only.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-7.2

Thanks!

[1/2] ASoC: sti: uniperif_reader: Use guard() for spin locks
      https://git.kernel.org/broonie/sound/c/205cc2a7eff0
[2/2] ASoC: sti: uniperif_player: Use guard() for mutex & spin locks
      https://git.kernel.org/broonie/sound/c/96166a8def74

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