Skip to content

Commit 8d9f738

Browse files
sterling-tengbroonie
authored andcommitted
regulator: fix bullet lists of regulator_ops comment
Since 89a6a5e("regulator: add property parsing and callbacks to set protection limits") which introduced a warning: Documentation/driver-api/regulator:166: ./include/linux/regulator/driver.h:96: WARNING: Unexpected indentation. Documentation/driver-api/regulator:166: ./include/linux/regulator/driver.h:98: WARNING: Block quote ends without a blank line; unexpected unindent. Let's fix them. Signed-off-by: Yanteng Si <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Mark Brown <[email protected]>
1 parent 8d2de3a commit 8d9f738

File tree

1 file changed

+13
-9
lines changed

1 file changed

+13
-9
lines changed

include/linux/regulator/driver.h

Lines changed: 13 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -90,15 +90,19 @@ enum regulator_detection_severity {
9090
* @set_over_current_protection: Support enabling of and setting limits for over
9191
* current situation detection. Detection can be configured for three
9292
* levels of severity.
93-
* REGULATOR_SEVERITY_PROT should automatically shut down the regulator(s).
94-
* REGULATOR_SEVERITY_ERR should indicate that over-current situation is
95-
* caused by an unrecoverable error but HW does not perform
96-
* automatic shut down.
97-
* REGULATOR_SEVERITY_WARN should indicate situation where hardware is
98-
* still believed to not be damaged but that a board sepcific
99-
* recovery action is needed. If lim_uA is 0 the limit should not
100-
* be changed but the detection should just be enabled/disabled as
101-
* is requested.
93+
*
94+
* - REGULATOR_SEVERITY_PROT should automatically shut down the regulator(s).
95+
*
96+
* - REGULATOR_SEVERITY_ERR should indicate that over-current situation is
97+
* caused by an unrecoverable error but HW does not perform
98+
* automatic shut down.
99+
*
100+
* - REGULATOR_SEVERITY_WARN should indicate situation where hardware is
101+
* still believed to not be damaged but that a board sepcific
102+
* recovery action is needed. If lim_uA is 0 the limit should not
103+
* be changed but the detection should just be enabled/disabled as
104+
* is requested.
105+
*
102106
* @set_over_voltage_protection: Support enabling of and setting limits for over
103107
* voltage situation detection. Detection can be configured for same
104108
* severities as over current protection. Units of uV.

0 commit comments

Comments
 (0)