On Mon, 7 Nov 2022 11:04:28 -0500, Nícolas F. R. A. Prado wrote: > Some ASoC machine drivers for MediaTek platforms were not being > registered to the module device table, preventing them to be > automatically loaded when built as modules. This series adds the missing > registration to the drivers. > > > Nícolas F. R. A. Prado (9): > ASoC: mediatek: mt2701-cs42448: Register to module device table > ASoC: mediatek: mt2701-wm8960: Register to module device table > ASoC: mediatek: mt6797-mt6351: Register to module device table > ASoC: mediatek: mt8183-da7219: Register to module device table > ASoC: mediatek: mt8183-mt6358: Register to module device table > ASoC: mediatek: mt8186-da7219: Register to module device table > ASoC: mediatek: mt8186-rt5682: Register to module device table > ASoC: mediatek: mt8192-mt6359: Register to module device table > ASoC: mediatek: mt8195-mt6359: Register to module device table > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/9] ASoC: mediatek: mt2701-cs42448: Register to module device table commit: f0f217ba7dea78872f5001135984159f4def7047 [2/9] ASoC: mediatek: mt2701-wm8960: Register to module device table commit: 59429a5ecc3337aaf6bbd878637250c1c878edc2 [3/9] ASoC: mediatek: mt6797-mt6351: Register to module device table commit: 083e948082def40d5d801a3e281d637ee3c0f9bf [4/9] ASoC: mediatek: mt8183-da7219: Register to module device table commit: b5e004b0e5b57d14ac7804875878cdfdb31c9288 [5/9] ASoC: mediatek: mt8183-mt6358: Register to module device table commit: bc63a806acdcfca201c68c820731d74185118789 [6/9] ASoC: mediatek: mt8186-da7219: Register to module device table commit: 7d6d41e5fbf5e96788c88c9e82a3898ad4cf4f3c [7/9] ASoC: mediatek: mt8186-rt5682: Register to module device table commit: 5d7c2ac0eb3e830a5c8e30515805b3a345d9b919 [8/9] ASoC: mediatek: mt8192-mt6359: Register to module device table commit: 2d32a3e52b0537638b31b3315ea1feafc5d0bb02 [9/9] ASoC: mediatek: mt8195-mt6359: Register to module device table commit: 6bd8ddf05e9a19fb9efebe46bf58f45b9a6af26a 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
