On Fri, 05 Apr 2024 11:09:16 +0200, Cezary Rojewski wrote: > Set of changes targeting the avs-driver only. No new features, patchset > either fixes or fortifies existing code. > > Patchset starts off with a fix for debugbility on ICL+ platforms which I > have forgotten to fixup when providing support for these initially. > The next two address copier module initialization, most importantly, > silence the gcc 'field-spanning write' false-positive. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [01/13] ASoC: Intel: avs: Restore stream decoupling on prepare commit: 680507581e025d16a0b6d3782603ca8c598fbe2b [02/13] ASoC: Intel: avs: Fix debug-slot offset calculation commit: c91b692781c1839fcc389b2a9120e46593c6424b [03/13] ASoC: Intel: avs: Silence false-positive memcpy() warnings commit: 6dd68c2da44d92c25b323bcc2603421463437a64 [04/13] ASoC: Intel: avs: Fix config_length for config-less copiers commit: beeeee9686affef32ee04d8ae30db8c53cbc7aee [05/13] ASoC: Intel: avs: Fix ASRC module initialization commit: 9d2e26f31c7cc3fa495c423af9b4902ec0dc7be3 [06/13] ASoC: Intel: avs: Replace risky functions with safer variants commit: 47714847592b574ff594ceca7ebe0ada70dbac3c [07/13] ASoC: Intel: avs: Fix potential integer overflow commit: c7e832cabe635df47c2bf6df7801e97bf3045b1e [08/13] ASoC: Intel: avs: Test result of avs_get_module_entry() commit: 41bf4525fadb3d8df3860420d6ac9025c51a3bac [09/13] ASoC: Intel: avs: Remove dead code commit: d58275f474b4a27b4e97839ffe8d9fe55c0cc40a [10/13] ASoC: Intel: avs: Wake from D0ix when starting streaming commit: 30df76bbcb59254ce646477e3e05f00021a10117 [11/13] ASoC: Intel: avs: Init debugfs before booting firmware commit: ff0aefe2d217ce6fec6487b225737b2019eb88c0 [12/13] ASoC: Intel: avs: Add assert_static to guarantee ABI sizes commit: c2b10acb62c195db2c976d614d9d8092ad6339ae [13/13] ASoC: Intel: avs: Rule invalid buffer and period sizes out commit: 9a385993504e47a0fd6fd34b5384827b4abdee60 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
