Message ID | 20230519195611.4068853-1-amadeuszx.slawinski@linux.intel.com |
---|---|
Headers | show |
Series | ASoC: topology: Clean up error messages handling | expand |
On Fri, 19 May 2023 21:56:06 +0200, Amadeusz Sławiński wrote: > Series of patches cleaning up error messages when loading topology. In > few places instead of logging in place of failure message is logged in > caller. Additionally there are places where both caller and failing > function log error, leading to unnecessary logs. Clean all of the above > up. > > Amadeusz Sławiński (5): > ASoC: topology: Log control load errors in soc_tplg_control_load() > ASoC: topology: Remove redundant logs > ASoC: topology: Do not split message string on multiple lines > ASoC: topology: Remove redundant log > ASoC: topology: Remove redundant log > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/5] ASoC: topology: Log control load errors in soc_tplg_control_load() commit: ec5dffcd428f54c117158c7b2cd79a1e14aa5b70 [2/5] ASoC: topology: Remove redundant logs commit: 2316c11fa97779d06bfd7990f45b13a7b6ec1dae [3/5] ASoC: topology: Do not split message string on multiple lines commit: 5308540278d776e10519db144cb0cf3b3dd7ffbf [4/5] ASoC: topology: Remove redundant log commit: f9d1fe7e81b87378e7bb4a0be9c6fb29bbaa73c0 [5/5] ASoC: topology: Remove redundant log commit: f9d1fe7e81b87378e7bb4a0be9c6fb29bbaa73c0 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