regulator: cleanup comments
Subsystems (3)
PATCH 1/1 regulator: cleanup comments
From: Tom Rix <[email protected]>
For spdx
Remove leading space, add space after //
Replacements
overriden to overridden
Calulate to Calculate
addional to additional
regulatior to regulator
devive to device
--- drivers/regulator/max8973-regulator.c | 2 +- drivers/regulator/sc2731-regulator.c | 2 +- drivers/regulator/ti-abb-regulator.c | 6 +++--- drivers/regulator/wm8350-regulator.c | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-)
drivers/regulator/max8973-regulator.c +1 -1
@@ -459,7 +459,7 @@ static int max8973_thermal_read_temp(void *data, int *temp)return ret; } -/* +1 degC to trigger cool devive */ +/* +1 degC to trigger cool device */ if (val &MAX77621_CHIPID_TJINT_S ) *temp = mchip->junction_temp_warning +1000 ;else
drivers/regulator/sc2731-regulator.c +1 -1
@@ -1,4 +1,4 @@ -//SPDX-License-Identifier: GPL-2.0 +// SPDX-License-Identifier: GPL-2.0 /* * Copyright (C) 2017 Spreadtrum Communications Inc. */
drivers/regulator/ti-abb-regulator.c +3 -3
@@ -42,7 +42,7 @@/** * struct ti_abb_info - ABB information per voltage setting * @opp_sel: one of TI_ABB macro -* @vset: (optional) vset value that LDOVBB needs to be overriden with. +* @vset: (optional) vset value that LDOVBB needs to be overridden with. * * Array of per voltage entries organized in the same order as regulator_desc's * volt_table list. (selector is used to index from this array)
@@ -484,7 +484,7 @@ static int ti_abb_init_timings(struct device *dev, struct ti_abb *abb)/* Calculate cycle rate */ cycle_rate =DIV_ROUND_CLOSEST (clock_cycles *10 , clk_rate); -/* Calulate SR2_WTCNT_VALUE */ +/* Calculate SR2_WTCNT_VALUE */ sr2_wt_cnt_val =DIV_ROUND_CLOSEST (abb->settling_time *10 , cycle_rate); dev_dbg(dev, "%s: Clk_rate=%ld, sr2_cnt=0x%08x\n", __func__,
@@ -688,7 +688,7 @@ MODULE_DEVICE_TABLE(of, ti_abb_of_match);* @pdev: ABB platform device * * Initializes an individual ABB LDO for required Body-Bias. ABB is used to -* addional bias supply to SoC modules for power savings or mandatory stability +* additional bias supply to SoC modules for power savings or mandatory stability * configuration at certain Operating Performance Points(OPPs). * * Return: 0 on success or appropriate error value when fails
drivers/regulator/wm8350-regulator.c +1 -1
@@ -1112,7 +1112,7 @@ static int wm8350_regulator_probe(struct platform_device *pdev)if (pdev->id <WM8350_DCDC_1 || pdev->id >WM8350_ISINK_B )return -ENODEV ; -/* do any regulatior specific init */ +/* do any regulator specific init */ switch (pdev->id) {case WM8350_DCDC_1 : val =wm8350_reg_read (wm8350,WM8350_DCDC1_LOW_POWER );
Signature · 1 line
2.26.3
Quoted 12 lines · On Sat, Mar 05, 2022 at 08:24:38AM -0800, [email protected] wrote:
From: Tom Rix <[email protected]>
For spdx
Remove leading space, add space after //Replacements
overriden to overridden
Calulate to Calculate
addional to additional
regulatior to regulator
devive to device
Quoted 2 lines
Signed-off-by Tom Rix <[email protected]>---
For wm8350:
Thanks,
Charles
Mark Brown
maintainerQuoted 5 lines · On Sat, 5 Mar 2022 08:24:38 -0800, [email protected] wrote:
From: Tom Rix <[email protected]>
For spdx
Remove leading space, add space after //
Quoted 8 lines
Replacements
overriden to overridden
Calulate to Calculate
addional to additional
regulatior to regulator
devive to device[...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/1] regulator: cleanup comments
commit: bbc7ba0fa06ab4aee26969a9454ca32e4a8fcb1c
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