On Wed, 17 Dec 2025 16:39:37 +0200, Peter Ujfalusi wrote:
Changes since v2:
- correct the fixes tag for the second path
Changes since v1:
- correct SHAs for fixes tags
- add Cc stable tag
[...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/8] ASoC: SOF: ipc4-control: If there is no data do not send bytes update commit: 2fa74713744dc5e908fff851c20f5f89fd665fb7 [2/8] ASoC: SOF: ipc4-topology: Correct the allocation size for bytes controls commit: a653820700b81c9e6f05ac23b7969ecec1a18e85 [3/8] ASoC: SOF: ipc4-control: Use the correct size for scontrol->ipc_control_data commit: c1876fc33c5976837e4c73719c7582617efc6919 [4/8] ASoC: SOF: ipc4-control: Keep the payload size up to date commit: ebcfdbe4add923dfb690e6fb9d158da87ae0b6bf [5/8] ASoC: SOF: ipc4-topology: Set initial param_id for bytes control type commit: 2fdde18a2cb1631c01e4ab87d949564c7d134dd8 [6/8] ASoC: SOF: ipc4: Support for sending payload along with LARGE_CONFIG_GET commit: d96cb0b86d6e8bbbbfa425771606f6c1aebc318e [7/8] ASoC: SOF: ipc4: Add definition for generic bytes control commit: 7fd8c216c422c5d42addc3e46d5d26630ff646d1 [8/8] ASoC: SOF: ipc4-control: Add support for generic bytes control commit: 2a28b5240f2b328495c6565d277f438dbc583d61
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