mbox series

[0/3] ASoC: ssm: Use modern ASoC DAI format terminology

Message ID 20220602130531.3552275-1-broonie@kernel.org (mailing list archive)
Headers show
Series ASoC: ssm: Use modern ASoC DAI format terminology | expand

Message

Mark Brown June 2, 2022, 1:05 p.m. UTC 
Trivial updates to modernise the various ssm* drivers to the new
DAI clocking constants.

Mark Brown (3):
  ASoC: ssm2518: Use modern ASoC DAI format terminology
  ASoC: ssm2602: Use modern ASoC DAI format terminology
  ASoC: ssm4567: Use modern ASoC DAI format terminology

 sound/soc/codecs/ssm2518.c | 4 ++--
 sound/soc/codecs/ssm2602.c | 6 +++---
 sound/soc/codecs/ssm4567.c | 4 ++--
 3 files changed, 7 insertions(+), 7 deletions(-)

Comments

Mark Brown June 7, 2022, 3:11 p.m. UTC | #1 
On Thu, 2 Jun 2022 15:05:28 +0200, Mark Brown wrote:
> Trivial updates to modernise the various ssm* drivers to the new
> DAI clocking constants.
> 
> Mark Brown (3):
>   ASoC: ssm2518: Use modern ASoC DAI format terminology
>   ASoC: ssm2602: Use modern ASoC DAI format terminology
>   ASoC: ssm4567: Use modern ASoC DAI format terminology
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: ssm2518: Use modern ASoC DAI format terminology
      commit: 8dc51d009fad7aba0575e0eb4b684d25c0f01f37
[2/3] ASoC: ssm2602: Use modern ASoC DAI format terminology
      commit: 0160e8835fab4d4a15abefe7509d0397890c0ffd
[3/3] ASoC: ssm4567: Use modern ASoC DAI format terminology
      commit: 627a18149250e13409079ffb6936e472c3766f44

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