On Fri, 6 May 2022 16:26:39 +0300, Peter Ujfalusi wrote: > The current IPC client infrastructure can only be used with IPC3. > This series carries updates for the core side of the client support to handle > IPC4 messages and updates the ipc message injector to be usable with IPC4. > > The IPC flood test is only supported by SOF_IPC (IPC3), we are not going to > create the aux device for it at all if the firmware is using IPC4. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/8] ASoC: SOF: sof-client: Add API to get the maximum IPC payload size commit: a669ec5f4bc485a56b2f379e7c7197a810872cc1 [2/8] ASoC: SOF: ipc-msg-injector: Query the maximum IPC payload size commit: ef368c3347fe79a4193317b130b02064801920d7 [3/8] ASoC: SOF: sof-client-probes: Query the maximum IPC payload size commit: a1e5bbc8ea6ae6e0fa1bd42f2ef810b13d9ec066 [4/8] ASoC: SOF: sof-client: Add API to get the ipc_type commit: cdf8233d2cd2e55c8bc409e5b4fbdb181a1dea2b [5/8] ASoC: SOF: sof-client: Add support IPC4 message sending commit: 100c9374318f881c3083573af9dc76afa229fd23 [6/8] ASoC: SOF: ipc-msg-injector: Separate the message sending commit: a9aa3381e404abae3dd8c37b7c845415b56f0305 [7/8] ASoC: SOF: ipc-msg-injector: Add support for IPC4 messages commit: 066c67624d8ca2a2465690d4a7b7f52b880e9925 [8/8] ASoC: SOF: sof-client: IPC flood test can only work with SOF_IPC commit: 5889ccdd094ac32ee52851fc9eccd124897daf2b 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
