regulator: dbx500: Remove unused debugfs goto label
PATCH v2 1/1 regulator: dbx500: Remove unused debugfs goto label
The following build warning is seen after commit 8bdaa43808b7 ("regulator:
dbx500: no need to check return value of debugfs_create functions"):
drivers/regulator/dbx500-prcmu.c:144:1: warning: label 'exit_no_debugfs' defined but not used [-Wunused-label]
Remove the unused label and its associated error message.
---
Changes since v1:
- Add a Fixes tag
- Put the Reported-by tag in the correct position
drivers/regulator/dbx500-prcmu.c | 2 -- 1 file changed, 2 deletions(-)
drivers/regulator/dbx500-prcmu.c +0 -2
@@ -141,8 +141,6 @@ ux500_regulator_debug_init(struct platform_device *pdev,kfree (rdebug.state_before_suspend); exit_destroy_power_state:debugfs_remove_recursive (rdebug.dir); -exit_no_debugfs: -dev_err (&pdev->dev,"failed to create debugfs entries.\n" );return -ENOMEM ; }
Signature · 1 line
2.17.1
Mark Brown
maintainerQuoted 6 lines · Fabio Estevam
The following build warning is seen after commit
8bdaa43808b7("regulator:
dbx500: no need to check return value ofdebugfs_createfunctions"):
drivers/regulator/dbx500-prcmu.c:144:1: warning: label 'exit_no_debugfs' defined but not used [-Wunused-label]Remove the unused label and its associated error message.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/1] regulator: dbx500: Remove unused debugfs goto label
commit: c0e53a448637366064d4b9ce586b68ced679cd22
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