Re: (subset) [PATCH 00/11] ASoC: codecs: Series of fixes for realtek codecs used on RVPs

From: Mark Brown <broonie@kernel.org>
To: amadeuszx.slawinski@linux.intel.com, oder_chiou@realtek.com
Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	cezary.rojewski@intel.com, tiwai@suse.com,
	alsa-devel@alsa-project.org, lgirdwood@gmail.com
Subject: Re: (subset) [PATCH 00/11] ASoC: codecs: Series of fixes for realtek codecs used on RVPs
Date: Fri, 10 Jun 2022 16:58:51 +0100	[thread overview]
Message-ID: <165487673193.1755957.10182060787861198748.b4-ty@kernel.org> (raw)
In-Reply-To: <20220609133541.3984886-1-amadeuszx.slawinski@linux.intel.com>

On Thu, 9 Jun 2022 15:35:30 +0200, Amadeusz Sławiński wrote:
> Our tests platforms do use realtek codecs, while implementing avs driver
> and machine boards for it, we identified quite a lot of problems with
> those codec drivers.
> 
> This series aims to fix those issues.
> 
> Amadeusz Sławiński (8):
>   ASoC: codecs: rt274: Move irq registration and cleanup
>   ASoC: codecs: rt286: Move irq registration and cleanup
>   ASoC: codecs: rt298: Move irq registration and cleanup
>   ASoC: codecs: rt274: Enable irq only when needed
>   ASoC: codecs: rt286: Enable irq only when needed
>   ASoC: codecs: rt298: Enable irq only when needed
>   ASoC: codecs: rt298: Fix NULL jack in interrupt
>   ASoC: codecs: rt298: Fix jack detection
> 
> [...]

Applied to

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

Thanks!

[01/11] ASoC: codecs: rt274: Always init jack_detect_work
        commit: a43b4394bb35391b74486a788be6634ed91e221a
[02/11] ASoC: codecs: rt286: Reorganize jack detect handling
        commit: 3082afe097cc5d794c28a629f3492a0133ee4891
[03/11] ASoC: codecs: rt298: Reorganize jack detect handling
        commit: 1eb73102da280b28bc3899f694e673bf3e4d0afd

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