From: Bart Van Assche <bvanassche@acm.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Bart Van Assche <bvanassche@acm.org>
Subject: [PATCH 1/4] block, documentation: Fix wbt_lat_usec documentation
Date: Fri, 28 Jun 2019 13:07:42 -0700 [thread overview]
Message-ID: <20190628200745.206110-2-bvanassche@acm.org> (raw)
In-Reply-To: <20190628200745.206110-1-bvanassche@acm.org>
Fix the spelling of the wbt_lat_usec sysfs attribute.
Fixes: 87760e5eef35 ("block: hook up writeback throttling") # v4.10.
Signed-off-by: Bart Van Assche <bvanassche@acm.org>
---
Documentation/block/queue-sysfs.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/block/queue-sysfs.txt b/Documentation/block/queue-sysfs.txt
index 83b457e24bba..3eaf86806621 100644
--- a/Documentation/block/queue-sysfs.txt
+++ b/Documentation/block/queue-sysfs.txt
@@ -185,8 +185,8 @@ This is the number of bytes the device can write in a single write-same
command. A value of '0' means write-same is not supported by this
device.
-wb_lat_usec (RW)
-----------------
+wbt_lat_usec (RW)
+-----------------
If the device is registered for writeback throttling, then this file shows
the target minimum read latency. If this latency is exceeded in a given
window of time (see wb_window_usec), then the writeback throttling will start
--
2.22.0.410.gd8fdbe21b5-goog
next prev parent reply other threads:[~2019-06-28 20:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 20:07 [PATCH 0/4] Improve block layer request queue sysfs parameter documentation Bart Van Assche
2019-06-28 20:07 ` Bart Van Assche [this message]
2019-06-28 20:22 ` [PATCH 1/4] block, documentation: Fix wbt_lat_usec documentation Martin K. Petersen
2019-06-28 20:07 ` [PATCH 2/4] block, documentation: Sort queue sysfs attribute names alphabetically Bart Van Assche
2019-06-28 20:22 ` Martin K. Petersen
2019-06-28 20:07 ` [PATCH 3/4] block, documentation: Explain the word 'segments' Bart Van Assche
2019-06-28 20:14 ` Martin K. Petersen
2019-06-28 20:07 ` [PATCH 4/4] block, documentation: Document discard_zeroes_data, fua, max_discard_segments and write_zeroes_max_bytes Bart Van Assche
2019-06-28 20:23 ` Martin K. Petersen
2019-06-29 15:38 ` [PATCH 0/4] Improve block layer request queue sysfs parameter documentation Jens Axboe
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=20190628200745.206110-2-bvanassche@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@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;
as well as URLs for NNTP newsgroup(s).