Linux block layer
 help / color / mirror / Atom feed
From: Jay Winston <jaybenjaminwinston@gmail.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	corbet@lwn.net, Jay Winston <jaybenjaminwinston@gmail.com>
Subject: [PATCH] Documentation: ABI: fix "unexpected indentation" error in sysfs-block
Date: Sun, 21 Jun 2026 09:02:02 +0300	[thread overview]
Message-ID: <20260621060235.12994-1-jaybenjaminwinston@gmail.com> (raw)

`make htmldocs` reports:
Documentation/ABI/stable/sysfs-block:612: ERROR: Unexpected indentation

Leading dashes at lines 623, 636, and 641 were considered line
continuation with errant indent and not bullet points due to
missing blank lines.  Add the blank lines.

Signed-off-by: Jay Winston <jaybenjaminwinston@gmail.com>
---
 Documentation/ABI/stable/sysfs-block | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/Documentation/ABI/stable/sysfs-block b/Documentation/ABI/stable/sysfs-block
index aa1e94169666..f4bce370a540 100644
--- a/Documentation/ABI/stable/sysfs-block
+++ b/Documentation/ABI/stable/sysfs-block
@@ -620,6 +620,7 @@ Description:
 		- async_depth is always equal to nr_requests.
 
 		For bfq scheduler:
+
 		- By default, async_depth is set to 75% of nr_requests.
 		  Internal limits are then derived from this value:
 		  * Sync writes: limited to async_depth (≈75% of nr_requests).
@@ -633,11 +634,13 @@ Description:
 		  these limits proportionally based on the new value.
 
 		For Kyber:
+
 		- By default async_depth is set to 75% of nr_requests.
 		- If the user writes a custom value to async_depth, then it override the
 		  default and directly control the limit for writes and async I/O.
 
 		For mq-deadline:
+
 		- By default async_depth is set to nr_requests.
 		- If the user writes a custom value to async_depth, then it override the
 		  default and directly control the limit for writes and async I/O.
-- 
2.46.4


                 reply	other threads:[~2026-06-21  6:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260621060235.12994-1-jaybenjaminwinston@gmail.com \
    --to=jaybenjaminwinston@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=corbet@lwn.net \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox