linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org
Subject: [PATCH 2/7] block: bio: delete duplicated words
Date: Thu, 30 Jul 2020 18:42:28 -0700	[thread overview]
Message-ID: <20200731014233.6418-3-rdunlap@infradead.org> (raw)
In-Reply-To: <20200731014233.6418-1-rdunlap@infradead.org>

Drop the repeated words "a" and "the".

Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org
---
 block/bio.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

--- linux-next-20200730.orig/block/bio.c
+++ linux-next-20200730/block/bio.c
@@ -862,7 +862,7 @@ EXPORT_SYMBOL(bio_add_pc_page);
  * @same_page: return if the segment has been merged inside the same page
  *
  * Try to add the data at @page + @off to the last bvec of @bio.  This is a
- * a useful optimisation for file systems with a block size smaller than the
+ * useful optimisation for file systems with a block size smaller than the
  * page size.
  *
  * Warn if (@len, @off) crosses pages in case that @same_page is true.
@@ -988,7 +988,7 @@ static int __bio_iov_bvec_add_pages(stru
  * Pins pages from *iter and appends them to @bio's bvec array. The
  * pages will have to be released using put_page() when done.
  * For multi-segment *iter, this function only adds pages from the
- * the next non-empty segment of the iov iterator.
+ * next non-empty segment of the iov iterator.
  */
 static int __bio_iov_iter_get_pages(struct bio *bio, struct iov_iter *iter)
 {

  parent reply	other threads:[~2020-07-31  1:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-31  1:42 [PATCH 0/7] block: delete or fix duplicated words Randy Dunlap
2020-07-31  1:42 ` [PATCH 1/7] block: bfq-iosched: fix duplicated word Randy Dunlap
2020-07-31  1:42 ` Randy Dunlap [this message]
2020-07-31  1:42 ` [PATCH 3/7] block: elevator: delete duplicated word and fix typos Randy Dunlap
2020-07-31  1:42 ` [PATCH 4/7] block: genhd: delete duplicated words Randy Dunlap
2020-07-31  1:42 ` [PATCH 5/7] block: blk-mq: delete duplicated word Randy Dunlap
2020-07-31  1:42 ` [PATCH 6/7] block: blk-mq-sched: " Randy Dunlap
2020-07-31  1:42 ` [PATCH 7/7] block: blk-timeout: " Randy Dunlap
2020-07-31 22:30 ` [PATCH 0/7] block: delete or fix duplicated words 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=20200731014233.6418-3-rdunlap@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@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).