mbox series

[0/2] ASoC: SOF: ipc4-topology: fix error and memory handling

Message ID 20220708200516.26853-1-pierre-louis.bossart@linux.intel.com
Headers show
Series ASoC: SOF: ipc4-topology: fix error and memory handling | expand

Message

Pierre-Louis Bossart July 8, 2022, 8:05 p.m. UTC
Two patches to improve error and memory handling. When IPC4 is used,
some of the flows were incorrect.

Libin Yang (2):
  ASoC: SOF: ipc4-topology: check dai->private in ipc_free()
  ASoC: SOF: ipc4-topology: free memories allocated in
    sof_ipc4_get_audio_fmt

 sound/soc/sof/ipc4-topology.c | 59 ++++++++++++++++++++++++++++++++---
 1 file changed, 55 insertions(+), 4 deletions(-)

Comments

Mark Brown July 11, 2022, 3:18 p.m. UTC | #1
On Fri, 8 Jul 2022 15:05:14 -0500, Pierre-Louis Bossart wrote:
> Two patches to improve error and memory handling. When IPC4 is used,
> some of the flows were incorrect.
> 
> Libin Yang (2):
>   ASoC: SOF: ipc4-topology: check dai->private in ipc_free()
>   ASoC: SOF: ipc4-topology: free memories allocated in
>     sof_ipc4_get_audio_fmt
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: SOF: ipc4-topology: check dai->private in ipc_free()
      commit: b737fd8cf196bc96e471304007c3cd9b78672069
[2/2] ASoC: SOF: ipc4-topology: free memories allocated in sof_ipc4_get_audio_fmt
      commit: dc4fc0ae94cf87f1017f158b6fa2b7536ef29b4e

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