[PATCH] mm: fix indentation of bdi sysfs description

Bagas Sanjaya
2022-11-22T09:24:39Z

Stephen Rothwell reported htmldocs warnings when merging mm tree:

Documentation/ABI/testing/sysfs-class-bdi:76: WARNING: Unexpected indentation.
Documentation/ABI/testing/sysfs-class-bdi:89: WARNING: Unexpected indentation.
Documentation/ABI/testing/sysfs-class-bdi:48: WARNING: Unexpected indentation.

These warnings are due to inconsistent indentation in description of bdi
sysfs symbols.

Fix these by following indentation of surrounding text.

Link: https://lore.kernel.org/linux-next/20221122175057.52f0cd9f@canb.auug.org.au/
Fixes: 93e6d447506d8a ("mm: document /sys/class/bdi//min_bytes knob")
Fixes: a0eef74439b213 ("mm: document /sys/class/bdi//max_ratio_fine knob")
Fixes: 3aafa9ff1d4f67 ("mm: document /sys/class/bdi//min_ratio_fine knob")
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
Documentation/ABI/testing/sysfs-class-bdi | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/Documentation/ABI/testing/sysfs-class-bdi b/Documentation/ABI/testing/sysfs-class-bdi
index b4ed0db680cf69..0d2abd88a18cbd 100644
--- a/Documentation/ABI/testing/sysfs-class-bdi
+++ b/Documentation/ABI/testing/sysfs-class-bdi
@@ -54,8 +54,8 @@ Description:

The 'min_ratio_fine' parameter allows assigning a minimum reserve
of the write-back cache to a particular device. The value is
- expressed as part of 1 million. For example, this is useful for
- providing a minimum QoS.
+ expressed as part of 1 million. For example, this is useful for
+ providing a minimum QoS.

(read-write)

@@ -78,10 +78,10 @@ Contact: Stefan Roesch <shr@devkernel.io>
Description:
Allows limiting a particular device to use not more than the
given value of the write-back cache. The value is given as part
- of 1 million. This is useful in situations where we want to avoid
- one device taking all or most of the write-back cache. For example
- in case of an NFS mount that is prone to get stuck, or a FUSE mount
- which cannot be trusted to play fair.
+ of 1 million. This is useful in situations where we want to avoid
+ one device taking all or most of the write-back cache. For example
+ in case of an NFS mount that is prone to get stuck, or a FUSE mount
+ which cannot be trusted to play fair.

(read-write)

@@ -95,7 +95,7 @@ Description:

The 'min_bytes' parameter allows assigning a minimum
percentage of the write-back cache to a particular device
- expressed in bytes.
+ expressed in bytes.
For example, this is useful for providing a minimum QoS.

(read-write)

base-commit: d45f43b2c12b5ec8492c48574cb015c63304161b
--
An old man doll... just what I always wanted! - Clara