Skip to contentSkip to conversation

regulator: Replace symbolic permissions with octal permissions

PATCH In review Jinchao Wang 2 participants 2 messages Jun 30, 2021 – Jul 12, 2021 Voltage and current regulator framework

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 regulator: Replace symbolic permissions with octal permissions

Resolve following checkpatch issue,
Replace symbolic permissions with octal permissions

---
 drivers/regulator/dbx500-prcmu.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/regulator/dbx500-prcmu.c +2 -2
index 8b70bfe88019..a45c1e1ac7ef 100644
@@ -117,11 +117,11 @@ ux500_regulator_debug_init(struct platform_device *pdev,
 	rdebug.dir = debugfs_create_dir("ux500-regulator", NULL);
 
 	/* create "status" file */
-	debugfs_create_file("status", S_IRUGO, rdebug.dir, &pdev->dev,
+	debugfs_create_file("status", 0444, rdebug.dir, &pdev->dev,
 			    &ux500_regulator_status_fops);
 
 	/* create "power-state-count" file */
-	debugfs_create_file("power-state-count", S_IRUGO, rdebug.dir,
+	debugfs_create_file("power-state-count", 0444, rdebug.dir,
 			    &pdev->dev, &ux500_regulator_power_state_cnt_fops);
 
 	rdebug.regulator_array = regulator_info;
Signature · 1 line
2.31.1
maintainer
#1 lore raw
Quoted 2 lines · Jinchao Wang

Resolve following checkpatch issue,
Replace symbolic permissions with octal permissions

Applied to

https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/1] regulator: Replace symbolic permissions with octal permissions

      commit: 894cda54a76d7c336b6f301bafe49bf6870d4697

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