From: Jens Axboe <axboe@kernel.dk>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: rdunlap@infradead.org
Subject: Re: [PATCH V3] blk-mq: Trivial typo fix and sentence construction for better readability
Date: Fri, 19 Mar 2021 14:27:33 -0600 [thread overview]
Message-ID: <771aa286-5270-9642-7d6d-9cdb2f7014f8@kernel.dk> (raw)
In-Reply-To: <20210319202359.8893-1-unixbhaskar@gmail.com>
On 3/19/21 2:23 PM, Bhaskar Chowdhury wrote:
>
> A typo fix and sentence reconstruction for better readability.
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
> ---
> Changes from V2:
> Thanks, Randy and Tom for the suggestion,mould it.
> Missed the subject line prefix of pattern,so added back
>
> block/blk-mq-tag.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/block/blk-mq-tag.c b/block/blk-mq-tag.c
> index 9c92053e704d..9da426d20f12 100644
> --- a/block/blk-mq-tag.c
> +++ b/block/blk-mq-tag.c
> @@ -373,8 +373,8 @@ static bool blk_mq_tagset_count_completed_rqs(struct request *rq,
> }
>
> /**
> - * blk_mq_tagset_wait_completed_request - wait until all completed req's
> - * complete funtion is run
> + * blk_mq_tagset_wait_completed_request - wait until all the req's
> + * functions completed their run
This is still nonsense, see reply to previous version.
--
Jens Axboe
next prev parent reply other threads:[~2021-03-19 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 20:23 [PATCH V3] blk-mq: Trivial typo fix and sentence construction for better readability Bhaskar Chowdhury
2021-03-19 20:27 ` Jens Axboe [this message]
2021-03-19 20:39 ` Bhaskar Chowdhury
2021-03-19 22:19 ` Jens Axboe
2021-03-19 22:55 ` Bhaskar Chowdhury
2021-03-19 22:56 ` 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=771aa286-5270-9642-7d6d-9cdb2f7014f8@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=unixbhaskar@gmail.com \
/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