Skip to contentSkip to conversation

ASoC: uniphier: Drop redundant error messages in probe

PATCH In review [email protected] 2 participants 2 messages Jul 10 – Jul 18

Subsystems (4)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 ASoC: uniphier: Drop redundant error messages in probe

From: bui duc phuc <[email protected]>

Return the error directly when the helper already reports the failure, avoiding duplicate log messages.

---
 sound/soc/uniphier/aio-cpu.c | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)
sound/soc/uniphier/aio-cpu.c +2 -6
index d3dba21b2d04..78c82bf42a8f 100644
@@ -795,16 +795,12 @@ int uniphier_aio_probe(struct platform_device *pdev)
 	ret = devm_snd_soc_register_component(dev, &uniphier_aio_component,
 					      chip->chip_spec->dais,
 					      chip->chip_spec->num_dais);
-	if (ret) {
-		dev_err(dev, "Register component failed.\n");
+	if (ret)
 		goto err_out_reset;
-	}
 
 	ret = uniphier_aiodma_soc_register_platform(pdev);
-	if (ret) {
-		dev_err(dev, "Register platform failed.\n");
+	if (ret)
 		goto err_out_reset;
-	}
 
 	return 0;
 
Signature · 1 line
2.43.0
maintainer
#1 lore raw
Quoted 1 line · On Fri, 10 Jul 2026 18:02:49 +0700, [email protected] wrote:

ASoC: uniphier: Drop redundant error messages in probe

Applied to

https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-7.3

Thanks!

[1/1] ASoC: uniphier: Drop redundant error messages in probe

      https://git.kernel.org/broonie/sound/c/c89b22faa9ba

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