linux-next: build warnings after merge of the mm tree
Subsystems (2)
Hi all,
After merging the mm tree, today's linux-next build (htmldocs) produced thess warnings:
/home/sfr/next/next/Documentation/ABI/testing/sysfs-class-bdi:76: ERROR: Unexpected indentation. /home/sfr/next/next/Documentation/ABI/testing/sysfs-class-bdi:89: ERROR: Unexpected indentation. /home/sfr/next/next/Documentation/ABI/testing/sysfs-class-bdi:48: ERROR: Unexpected indentation.
Introduced by commit
93e6d447506d ("mm: document /sys/class/bdi/<bdi>/min_bytes knob") a0eef74439b2 ("mm: document /sys/class/bdi/<bdi>/max_ratio_fine knob") 3aafa9ff1d4f ("mm: document /sys/class/bdi/<bdi>/min_ratio_fine knob")
Signature · 2 lines
Cheers, Stephen Rothwell
PATCH 1/1 mm: fix indentation of bdi sysfs description
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.
--- Documentation/ABI/testing/sysfs-class-bdi | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-)
Documentation/ABI/testing/sysfs-class-bdi +7 -7
@@ -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 <[email protected]> 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
Signature · 1 line
An old man doll... just what I always wanted! - Clara