lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:   Sun,  5 Dec 2021 21:15:03 +0800
From:   Yanteng Si <siyanteng01@...il.com>
To:     lgirdwood@...il.com
Cc:     broonie@...nel.org, linux-kernel@...r.kernel.org, corbet@....net,
        chenhuacai@...nel.org, linux-doc@...r.kernel.org,
        siyanteng01@...il.com, Yanteng Si <siyanteng@...ngson.cn>
Subject: [PATCH] regulato: remove unnecessary indentation from driver.h's comments

Fix doc build warning as:

linux-next/Documentation/driver-api/regulator:166: ./include/linux/regulator/driver.h:96: WARNING: Unexpected indentation.
linux-next/Documentation/driver-api/regulator:166: ./include/linux/regulator/driver.h:98: WARNING: Block quote ends without a blank line; unexpected unindent.

Signed-off-by: Yanteng Si <siyanteng@...ngson.cn>
---
 include/linux/regulator/driver.h | 13 ++++++-------
 1 file changed, 6 insertions(+), 7 deletions(-)

diff --git a/include/linux/regulator/driver.h b/include/linux/regulator/driver.h
index 66219b174a8a..f777e259facd 100644
--- a/include/linux/regulator/driver.h
+++ b/include/linux/regulator/driver.h
@@ -92,13 +92,12 @@ enum regulator_detection_severity {
  *	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.
+ *	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.
-- 
2.27.0

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ