[v2,0/2] ASoC DPCM lockdep fixes

Message

Takashi Iwai Jan. 19, 2022, 3:52 p.m. UTC

Hi,

this is the revised patches for addressing ASoC lockdep warnings due
to the recent DPCM locking refactoring.


Takashi

v1->v2:
  - minor correction in the changelog for nested lock
  - debugfs removal workaround

===

Takashi Iwai (2):
  ASoC: soc-pcm: Fix DPCM lockdep warning due to nested stream locks
  ASoC: soc-pcm: Move debugfs removal out of spinlock

 include/sound/pcm.h     | 15 +++++++++++++++
 sound/core/pcm_native.c | 13 +++++++++++++
 sound/soc/soc-pcm.c     | 18 ++++++++++++------
 3 files changed, 40 insertions(+), 6 deletions(-)

Comments

Mark Brown Jan. 28, 2022, 11:46 p.m. UTC | #1

On Wed, 19 Jan 2022 16:52:47 +0100, Takashi Iwai wrote:
> this is the revised patches for addressing ASoC lockdep warnings due
> to the recent DPCM locking refactoring.
> 
> 
> Takashi
> 
> v1->v2:
>   - minor correction in the changelog for nested lock
>   - debugfs removal workaround
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: soc-pcm: Fix DPCM lockdep warning due to nested stream locks
      commit: 3c75c0ea5da749bd1efebd1387f2e5011b8c7d78
[2/2] ASoC: soc-pcm: Move debugfs removal out of spinlock
      commit: 9f620684c1ef5a002b6622ecc7b5818e81252f48

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