Re: [PATCH v3 00/12] ASoC: mediatek: mt8189: Improve error handling

[Mark Brown]

On Wed, 16 Sep 2026 12:00:07 +0700, phucduc.bui@xxxxxxxxx wrote:
> ASoC: mediatek: mt8189: Improve error handling
> 
> From: bui duc phuc <phucduc.bui@xxxxxxxxx>
> 
> Hi all,
> 
> This series addresses part of the error handling in the MT8189 AFE driver.
> 
> [...]

Applied to

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

Thanks!

[01/12] ASoC: mediatek: mt8189: Propagate APLL enable errors
        https://git.kernel.org/broonie/sound/c/5a3c23d4aa89
[02/12] ASoC: mediatek: mt8189: Propagate MCK enable errors
        https://git.kernel.org/broonie/sound/c/bd9a8d9def20
[03/12] ASoC: mediatek: mt8189: Validate MCK ID
        https://git.kernel.org/broonie/sound/c/b6b47040e897
[04/12] ASoC: mediatek: mt8189: Propagate reg_rw clock errors
        https://git.kernel.org/broonie/sound/c/29de66668799
[05/12] ASoC: mediatek: mt8189: Use dev_err_probe() for clock errors
        https://git.kernel.org/broonie/sound/c/ea8c96a05da7
[06/12] ASoC: mediatek: mt8189: Propagate runtime resume errors
        https://git.kernel.org/broonie/sound/c/483e827b005f
[07/12] ASoC: mediatek: mt8189: Remove redundant error message
        https://git.kernel.org/broonie/sound/c/e9e9e514eeef
[08/12] ASoC: mediatek: mt8189: Propagate APLL errors
        https://git.kernel.org/broonie/sound/c/6347f276da8c
[09/12] ASoC: mediatek: mt8189: Propagate MCLK errors
        https://git.kernel.org/broonie/sound/c/65b9d4a783cc
[10/12] ASoC: mediatek: mt8189: Validate sysclk frequency
        https://git.kernel.org/broonie/sound/c/9c73b5a43c99
[11/12] ASoC: mediatek: mt8189: Propagate TDM clock errors
        https://git.kernel.org/broonie/sound/c/242d0280eabb
[12/12] ASoC: mediatek: mt8189: Validate TDM MCLK frequency
        https://git.kernel.org/broonie/sound/c/197ec30e1b60

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