Re: [PATCH 0/8] ASoC: SOF: ipc4-topology: Rework the module audio format prints

[Mark Brown <broonie@xxxxxxxxxx>]

On Tue, 08 Oct 2024 14:09:28 +0300, Peter Ujfalusi wrote:
> When the audio started we print out here and there the Input and Output or only
> the Input audio format for the module that is in path of the stream.
> This is mostly OK but provides inconsistent an - in my opinion - hard to grasp
> information.
> 
> The series reworks how the input/output format is selected and tries to improve
> the consistency of the prints by applying universal rules:
> 
> [...]

Applied to

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

Thanks!

[1/8] ASoC: SOF: ipc4-topology: Drop the 'index' from 'Pin index' of format print
      commit: 76733db0f5560efa0c6514329620b9cbc8b1ca42
[2/8] ASoC: SOF: ipc4-topology: Use local variables in sof_ipc4_init_input_audio_fmt()
      commit: 3b54c1cd69d04bbdafc5542d11c6cab685fc13bd
[3/8] ASoC: SOF: ipc4-topology: Remove redundant check in sof_ipc4_init_input_audio_fmt()
      commit: 2d9635b57b1bbbece2a8d30103fcd1ebfbbe0178
[4/8] ASoC: SOF: ipc4-topology: Simplify match format print in sof_ipc4_init_input_audio_fmt()
      commit: 0126a659fd517103e8ce4d432fbe9b06f0a20510
[5/8] ASoC: SOF: ipc4-topology: Use local variables in sof_ipc4_init_output_audio_fmt()
      commit: 7a4c41e4778342b0ceda2e16127fefa808de3c57
[6/8] ASoC: SOF: ipc4-topology: Simplify code to deal with process modules without output
      commit: fdaf2291524c6a220bb051ad1a8d3c99b177b6f1
[7/8] ASoC: SOF: ipc4-topology: Concentrate prints inside of sof_ipc4_init_output_audio_fmt()
      commit: 22408b8f625d85b5453fde8627aa6dd49f87c281
[8/8] ASoC: SOF: ipc4-topology: Add helper function to print the module's in/out audio format
      commit: 47701a85af0c0d655e06dd23f6b8761848147450

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