[0/4] ASoC: SOF: cppcheck fixes and debugfs addition

Message

Pierre-Louis Bossart April 2, 2024, 2:59 p.m. UTC

Small changes with 3 cppcheck fixes and the firmware version now
visible with debugfs instead of only via dmesg logs.

Pierre-Louis Bossart (3):
  ASoC: SOF: amd: acp-loader: abort firmware download on write error
  ASoC: SOF: ipc4-priv: align prototype and function declaration
  ASoC: SOF: ipc4-topology: remove shadowed variable

Yong Zhi (1):
  ASoC: SOF: ipc4-loader: save FW version info to debugfs

 sound/soc/sof/amd/acp-loader.c | 2 ++
 sound/soc/sof/ipc4-loader.c    | 8 ++++++++
 sound/soc/sof/ipc4-priv.h      | 2 +-
 sound/soc/sof/ipc4-topology.c  | 1 -
 4 files changed, 11 insertions(+), 2 deletions(-)

Comments

Mark Brown April 2, 2024, 11:29 p.m. UTC | #1

On Tue, 02 Apr 2024 09:59:55 -0500, Pierre-Louis Bossart wrote:
> Small changes with 3 cppcheck fixes and the firmware version now
> visible with debugfs instead of only via dmesg logs.
> 
> Pierre-Louis Bossart (3):
>   ASoC: SOF: amd: acp-loader: abort firmware download on write error
>   ASoC: SOF: ipc4-priv: align prototype and function declaration
>   ASoC: SOF: ipc4-topology: remove shadowed variable
> 
> [...]

Applied to

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

Thanks!

[1/4] ASoC: SOF: ipc4-loader: save FW version info to debugfs
      commit: f690cdcc01a5b549715fefe22a98962e7672516b
[2/4] ASoC: SOF: amd: acp-loader: abort firmware download on write error
      commit: dbb6ca68b55ddf23d0b6de782c7641624a285fc2
[3/4] ASoC: SOF: ipc4-priv: align prototype and function declaration
      commit: 458e3870507f7ebd26a2f5c7e925d5b31a873114
[4/4] ASoC: SOF: ipc4-topology: remove shadowed variable
      commit: c143cfe4f87070f11d7550b38f72625b51bf229f

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