Message ID | 20220602135316.3554400-1-broonie@kernel.org (mailing list archive) |
---|---|
Headers | show |
Series | ASoC: DAI clocking terminology modernisation | expand |
On Thu, 2 Jun 2022 15:52:56 +0200, Mark Brown wrote: > Update the last batch of CODEC drivers without specific > maintainers to use the new defines for DAI clocking. > > Mark Brown (20): > ASoC: cx2072x: Use modern ASoC DAI format terminology > ASoC: max98090: Use modern ASoC DAI format terminology > ASoC: rk3328: Use modern ASoC DAI format terminology > ASoC: sta32x: Use modern ASoC DAI format terminology > ASoC: sta350: Use modern ASoC DAI format terminology > ASoC: sti-sas: Use modern ASoC DAI format terminology > ASoC: tas2552: Use modern ASoC DAI format terminology > ASoC: tas2770: Use modern ASoC DAI format terminology > ASoC: tas5086: Use modern ASoC DAI format terminology > ASoC: tas5720: Use modern ASoC DAI format terminology > ASoC: tas6424: Use modern ASoC DAI format terminology > ASoC: uda1334: Use modern ASoC DAI format terminology > ASoC: tlv320adc3xxx: Use modern ASoC DAI format terminology > ASoC: tlv320adcx140: Use modern ASoC DAI format terminology > ASoC: tlv320aic23: Use modern ASoC DAI format terminology > ASoC: tlv320aic26: Use modern ASoC DAI format terminology > ASoC: tlv320aic31xx: Use modern ASoC DAI format terminology > ASoC: tlv320aic32x4: Use modern ASoC DAI format terminology > ASoC: tlv320aic33: Use modern ASoC DAI format terminology > ASoC: tlv320dac3x: Use modern ASoC DAI format terminology > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [01/20] ASoC: cx2072x: Use modern ASoC DAI format terminology commit: eff8f2aeaf0c1b529d918c9f9569577dff600dc5 [02/20] ASoC: max98090: Use modern ASoC DAI format terminology commit: 573a9a37b6fcef6dc3977ca11a671f82b1c1b606 [03/20] ASoC: rk3328: Use modern ASoC DAI format terminology commit: cd0df1706d181bf103d0f02e6c008c2386772eb1 [04/20] ASoC: sta32x: Use modern ASoC DAI format terminology commit: ef08b481ae78eb89672bdf67ed306a43065253b3 [05/20] ASoC: sta350: Use modern ASoC DAI format terminology commit: def5b3774a48ed06e69b56af8317cb563bbd9ceb [06/20] ASoC: sti-sas: Use modern ASoC DAI format terminology commit: d7e98b570e801375130ed4796bcbb35a39669d44 [07/20] ASoC: tas2552: Use modern ASoC DAI format terminology commit: 6b486af2ab946cbcad5c95f8daa1f4a8a53f25c5 [08/20] ASoC: tas2770: Use modern ASoC DAI format terminology commit: f8a4018c826fde6137425bbdbe524d5973feb173 [09/20] ASoC: tas5086: Use modern ASoC DAI format terminology commit: 7c5c399fb97e3f7a88d1b154f610cab4d9253955 [10/20] ASoC: tas5720: Use modern ASoC DAI format terminology commit: 9f6654c3162a4e64265c62bea433550fce4beffd [11/20] ASoC: tas6424: Use modern ASoC DAI format terminology commit: f025fcc466cc03fa4f5ae245b6848629b846edff [12/20] ASoC: uda1334: Use modern ASoC DAI format terminology commit: 5fc4ed4bda465fb826bea7c6a7b15657154787ce [13/20] ASoC: tlv320adc3xxx: Use modern ASoC DAI format terminology commit: ad60ff09801fa1841dcdcf1f6ad1fa0e09ad0693 [14/20] ASoC: tlv320adcx140: Use modern ASoC DAI format terminology commit: 10649fa392c9abb6e9b258f7af9577596339fbe2 [15/20] ASoC: tlv320aic23: Use modern ASoC DAI format terminology commit: b9ff35c7afc6ae1bddca3f84fb23a3d903a62a23 [16/20] ASoC: tlv320aic26: Use modern ASoC DAI format terminology commit: 8d322f170b09989f47614c1a663371647f03176f [17/20] ASoC: tlv320aic31xx: Use modern ASoC DAI format terminology commit: 2fd8298aed2228b8c6b94edf820121da25b3f5e2 [18/20] ASoC: tlv320aic32x4: Use modern ASoC DAI format terminology commit: 0cc5a137f7a3ba6fec069d8d222020f0927a18ef [19/20] ASoC: tlv320aic33: Use modern ASoC DAI format terminology commit: 83a5f86903fbaf9c47c13975eb6f2fbd16d7f865 [20/20] ASoC: tlv320dac3x: Use modern ASoC DAI format terminology commit: 894bf75bb1f6c274cdd877879d9215abd6ed4b1b 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