Re: [PATCH 0/6] ASoC: rt-sdw: always cancel jack work on remove

[Mark Brown]

On Fri, 25 Sep 2026 22:50:12 +0800, Jiale Yao wrote:
> ASoC: rt-sdw: always cancel jack work on remove
> 
> The Realtek SoundWire codec remove callbacks cancel jack work only while
> hw_init is true. hw_init is cleared by update_status() when the slave
> becomes unattached, but jack work can already have been queued by the
> interrupt callback or jack initialization path. If remove runs after that
> state transition, the pending work is not drained and can run after the
> codec private data has been freed.
> 
> [...]

Applied to

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

Thanks!

[1/6] ASoC: rt5682-sdw: always cancel jack work on remove
      https://git.kernel.org/broonie/sound/c/9a98f7e955d3
[2/6] ASoC: rt711-sdw: always cancel jack work on remove
      https://git.kernel.org/broonie/sound/c/4bf78e3d9e32
[3/6] ASoC: rt711-sdca: always cancel jack work on remove
      https://git.kernel.org/broonie/sound/c/ecc2fca6dece
[4/6] ASoC: rt712-sdca: always cancel jack work on remove
      https://git.kernel.org/broonie/sound/c/c7d07df95ee7
[5/6] ASoC: rt721-sdca: always cancel jack work on remove
      https://git.kernel.org/broonie/sound/c/958d025d6235
[6/6] ASoC: rt722-sdca: always cancel jack work on remove
      https://git.kernel.org/broonie/sound/c/9d29132d81a7

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