[PATCH] docs: block: blk-mq.rst: correct drive -> driver

[PATCH] docs: block: blk-mq.rst: correct drive -> driver

[Yue Hu]

From: Yue Hu <huyue2@yulong.com>

It is 'driver' to complete the request. Also remove a redundant space.

Signed-off-by: Yue Hu <huyue2@yulong.com>
---
 Documentation/block/blk-mq.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/block/blk-mq.rst b/Documentation/block/blk-mq.rst
index a980d23..d96118c 100644
--- a/Documentation/block/blk-mq.rst
+++ b/Documentation/block/blk-mq.rst
@@ -62,7 +62,7 @@ queue, to be sent in the future, when the hardware is able.
 Software staging queues
 ~~~~~~~~~~~~~~~~~~~~~~~
 
-The block IO subsystem adds requests  in the software staging queues
+The block IO subsystem adds requests in the software staging queues
 (represented by struct blk_mq_ctx) in case that they weren't sent
 directly to the driver. A request is one or more BIOs. They arrived at the
 block layer through the data structure struct bio. The block layer
@@ -132,7 +132,7 @@ In order to indicate which request has been completed, every request is
 identified by an integer, ranging from 0 to the dispatch queue size. This tag
 is generated by the block layer and later reused by the device driver, removing
 the need to create a redundant identifier. When a request is completed in the
-drive, the tag is sent back to the block layer to notify it of the finalization.
+driver, the tag is sent back to the block layer to notify it of the finalization.
 This removes the need to do a linear search to find out which IO has been
 completed.
 
-- 
1.9.1

Re: [PATCH] docs: block: blk-mq.rst: correct drive -> driver

[Jonathan Corbet]

Yue Hu <zbestahu@gmail.com> writes:

> From: Yue Hu <huyue2@yulong.com>
>
> It is 'driver' to complete the request. Also remove a redundant space.
>
> Signed-off-by: Yue Hu <huyue2@yulong.com>
> ---
>  Documentation/block/blk-mq.rst | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/block/blk-mq.rst b/Documentation/block/blk-mq.rst
> index a980d23..d96118c 100644
> --- a/Documentation/block/blk-mq.rst
> +++ b/Documentation/block/blk-mq.rst
> @@ -62,7 +62,7 @@ queue, to be sent in the future, when the hardware is able.
>  Software staging queues
>  ~~~~~~~~~~~~~~~~~~~~~~~
>  
> -The block IO subsystem adds requests  in the software staging queues
> +The block IO subsystem adds requests in the software staging queues
>  (represented by struct blk_mq_ctx) in case that they weren't sent
>  directly to the driver. A request is one or more BIOs. They arrived at the
>  block layer through the data structure struct bio. The block layer
> @@ -132,7 +132,7 @@ In order to indicate which request has been completed, every request is
>  identified by an integer, ranging from 0 to the dispatch queue size. This tag
>  is generated by the block layer and later reused by the device driver, removing
>  the need to create a redundant identifier. When a request is completed in the
> -drive, the tag is sent back to the block layer to notify it of the finalization.
> +driver, the tag is sent back to the block layer to notify it of the finalization.
>  This removes the need to do a linear search to find out which IO has been
>  completed.

Applied, thanks.

jon