regulator: fix bullet lists of regulator_ops comment

Since 89a6a5e56c82("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 <siyanteng@loongson.cn>
Link: https://lore.kernel.org/r/20211207123230.2262047-1-siyanteng@loongson.cn
Signed-off-by: Mark Brown <broonie@kernel.org>

diff --git a/include/linux/regulator/driver.h b/include/linux/regulator/driver.h
index 4078c77764532a577d321ae82186ac2c4f08515f..720684995a776ae767f756feb1ae28f2ad4dca12 100644 (file)
--- a/include/linux/regulator/driver.h
+++ b/include/linux/regulator/driver.h
@@ -90,15 +90,19 @@ enum regulator_detection_severity {
  * @set_over_current_protection: Support enabling of and setting limits for over
  *     current situation detection. Detection can be configured for three
  *     levels of severity.
- *     REGULATOR_SEVERITY_PROT should automatically shut down the regulator(s).
- *     REGULATOR_SEVERITY_ERR should indicate that over-current situation is
- *             caused by an unrecoverable error but HW does not perform
- *             automatic shut down.
- *     REGULATOR_SEVERITY_WARN should indicate situation where hardware is
- *             still believed to not be damaged but that a board sepcific
- *             recovery action is needed. If lim_uA is 0 the limit should not
- *             be changed but the detection should just be enabled/disabled as
- *             is requested.
+ *
+ *     - REGULATOR_SEVERITY_PROT should automatically shut down the regulator(s).
+ *
+ *     - REGULATOR_SEVERITY_ERR should indicate that over-current situation is
+ *               caused by an unrecoverable error but HW does not perform
+ *               automatic shut down.
+ *
+ *     - REGULATOR_SEVERITY_WARN should indicate situation where hardware is
+ *               still believed to not be damaged but that a board sepcific
+ *               recovery action is needed. If lim_uA is 0 the limit should not
+ *               be changed but the detection should just be enabled/disabled as
+ *               is requested.
+ *
  * @set_over_voltage_protection: Support enabling of and setting limits for over
  *     voltage situation detection. Detection can be configured for same
  *     severities as over current protection. Units of uV.