Message ID | 20220707125701.3518263-1-amadeuszx.slawinski@linux.intel.com (mailing list archive) |
---|---|
Headers | show |
Series | ASoC: codecs: Series of fixes for realtek codecs used on RVPs | expand |
On Thu, 7 Jul 2022 14:56:56 +0200, Amadeusz Sławiński wrote: > Our tests platforms do use realtek codecs, while implementing avs driver > and machine boards for it, we identified some problems with those codec > drivers. > > This series aims to fix those issues. > > Changes in v2: > - Drop patches which were merged from v1 > - Drop patches changing IRQ behaviour > - Add patches to set component to NULL on remove - disabling IRQs > worked around the problem, so those patches weren't needed in earlier > series > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/5] ASoC: codecs: rt298: Fix NULL jack in interrupt commit: 9b6803ec1fe0f10942b9297d2d60ec46f2999323 [2/5] ASoC: codecs: rt298: Fix jack detection commit: c0c5a242bba878b4d34f7c9612fd6cd6c404d414 [3/5] ASoC: codecs: rt286: Set component to NULL on remove commit: c1d7ebda11aae4659b665af61d7277dd351659b9 [4/5] ASoC: codecs: rt298: Set component to NULL on remove commit: af3b33b9707d453a12e0cf5ac35d7b97b3524ace [5/5] ASoC: codecs: rt274: Set component to NULL on remove commit: b9f098aa7ae2a022dee06a8ca363e3e0e077f05a 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