On Tue, 12 Jul 2022 15:23:54 +0300, Peter Ujfalusi wrote: > By mistake a developer managed to create a 'corrupted' IPC4 firmware image which > loaded fine to the DSP and after boot it sent an IPC reply before we would have > received the FW_READY message. > It turned out that the image was an IPC3 firmware and the IPC reply was the IPC3 > FW_READY notification message which got understood as an IPC4 reply message due > to the difference between the two IPC mechanism. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/3] ASoC: SOF: Intel: cnl: Do not process IPC reply before firmware boot commit: acacd9eefd0def5a83244d88e5483b5f38ee7287 [2/3] ASoC: SOF: Intel: hda-ipc: Do not process IPC reply before firmware boot commit: 499cc881b09c8283ab5e75b0d6d21cb427722161 [3/3] ASoC: SOF: Intel: mtl: Do not process IPC reply before firmware boot commit: 1549a69b89b7e5b1b830da897529344766728a4b 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
