mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
	axboe@kernel.dk, linux-block@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] block: Few spelling fixes in the file blk-merge.c
Date: Sun, 14 Mar 2021 19:26:33 -0700	[thread overview]
Message-ID: <4f8b61d9-dc3a-7ba2-2f49-4a596f19d385@infradead.org> (raw)
In-Reply-To: <20210315011849.3964886-1-unixbhaskar@gmail.com>

On 3/14/21 6:18 PM, Bhaskar Chowdhury wrote:
> 
> 
> s/trival/trivial/
> s/attributs/attributes/
> 
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>

Acked-by: Randy Dunlap <rdunlap@infradead.org>

> ---
>  block/blk-merge.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/block/blk-merge.c b/block/blk-merge.c
> index 808768f6b174..a39327e38276 100644
> --- a/block/blk-merge.c
> +++ b/block/blk-merge.c
> @@ -283,7 +283,7 @@ static struct bio *blk_bio_segment_split(struct request_queue *q,
>  	/*
>  	 * Bio splitting may cause subtle trouble such as hang when doing sync
>  	 * iopoll in direct IO routine. Given performance gain of iopoll for
> -	 * big IO can be trival, disable iopoll when split needed.
> +	 * big IO can be trivial, disable iopoll when split needed.
>  	 */
>  	bio->bi_opf &= ~REQ_HIPRI;
> 
> @@ -675,7 +675,7 @@ void blk_rq_set_mixed_merge(struct request *rq)
>  	/*
>  	 * @rq will no longer represent mixable attributes for all the
>  	 * contained bios.  It will just track those of the first one.
> -	 * Distributes the attributs to each bio.
> +	 * Distributes the attributes to each bio.
>  	 */
>  	for (bio = rq->bio; bio; bio = bio->bi_next) {
>  		WARN_ON_ONCE((bio->bi_opf & REQ_FAILFAST_MASK) &&
> --


-- 
~Randy


      reply	other threads:[~2021-03-15  2:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-15  1:18 Bhaskar Chowdhury
2021-03-15  2:26 ` Randy Dunlap [this message]

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=4f8b61d9-dc3a-7ba2-2f49-4a596f19d385@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®