Documentation: block: blk-mq: Fix small typo in multi-queue docs
Subsystems (2)
PATCH 1/1 Documentation: block: blk-mq: Fix small typo in multi-queue docs
Fixed a small typo in the documentation for multi-queue block IO.
Signed-off-by Jinay Jain <[email protected]>
--- Documentation/block/blk-mq.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/block/blk-mq.rst +1 -1
@@ -54,7 +54,7 @@ layer or if we want to try to merge requests. In both cases, requests will be sent to the software queue. Then, after the requests are processed by software queues, they will be placed -at the hardware queue, a second stage queue were the hardware has direct access +at the hardware queue, a second stage queue where the hardware has direct access to process those requests. However, if the hardware does not have enough resources to accept more requests, blk-mq will places requests on a temporary queue, to be sent in the future, when the hardware is able.
Signature · 1 line
2.25.1
Quoted 12 lines · Jinay Jain
Fixed a small typo in the documentation for multi-queue block IO.
Signed-off-by Jinay Jain <[email protected]>--- Documentation/block/blk-mq.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)Documentation/block/blk-mq.rst +0
-0
Documentation/block/blk-mq.rst layer or if we want to try to merge requests. In both cases, requests will be · line 58
Quoted 6 lines
Documentation/block/blk-mq.rst +1
-1@@ -54,7 +54,7 @@ layer or if we want to try to merge requests. In both cases, requests will be sent to the software queue. Then, after the requests are processed by software queues, they will be placed -at the hardware queue, a second stage queue were the hardware has direct access +at the hardware queue, a second stage queue where the hardware has direct access to process those requests. However, if the hardware does not have enough
Applied, thanks.
jon