On Tue, 7 Jul 2020 15:37:44 -0500, Pierre-Louis Bossart wrote:
While experimenting and introducing errors in Baytrail topology files until I got them right, I encountered multiple kernel oopses and memory leaks. This is a first batch to harden the code, but we should probably think of a tool to fuzz the topology...
Pierre-Louis Bossart (5): ASoC: topology: fix kernel oops on route addition error ASoC: topology: fix tlvs in error handling for widget_dmixer ASoC: topology: use break on errors, not continue ASoC: topology: factor kfree(se) in error handling ASoC: topology: add more logs when topology load fails.
[...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/5] ASoC: topology: fix kernel oops on route addition error commit: 6f0307df83f2aa6bdf656c2219c89ce96502d20e [2/5] ASoC: topology: fix tlvs in error handling for widget_dmixer commit: 8edac489e7c3fce44208373bb3e7b5835a672c66 [3/5] ASoC: topology: use break on errors, not continue commit: 129fc2ba01c8322575173cc97afa324e54a5d4ce [4/5] ASoC: topology: factor kfree(se) in error handling commit: 952bd9377ef61c843236fd3e7cf65076025e26a4 [5/5] ASoC: topology: add more logs when topology load fails. commit: 8bf9475fe49fa96eea57724bb04e0931d101bc5a
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