public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicky Chorley <ndchorley@gmail.com>
To: axboe@kernel.dk, linux-block@vger.kernel.org
Cc: Nicky Chorley <ndchorley@gmail.com>
Subject: [PATCH] block: Fix some typos
Date: Sun, 14 Jan 2024 08:25:32 +0000	[thread overview]
Message-ID: <20240114082532.10751-1-ndchorley@gmail.com> (raw)

Correct some minor typos in blk-core.c.

Signed-off-by: Nicky Chorley <ndchorley@gmail.com>
---
 block/blk-core.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/block/blk-core.c b/block/blk-core.c
index 11342af420d0..8fa002bf1017 100644
--- a/block/blk-core.c
+++ b/block/blk-core.c
@@ -839,7 +839,7 @@ EXPORT_SYMBOL(submit_bio_noacct);
  *
  * submit_bio() is used to submit I/O requests to block devices.  It is passed a
  * fully set up &struct bio that describes the I/O that needs to be done.  The
- * bio will be send to the device described by the bi_bdev field.
+ * bio will be sent to the device described by the bi_bdev field.
  *
  * The success/failure status of the request, along with notification of
  * completion, is delivered asynchronously through the ->bi_end_io() callback
@@ -934,8 +934,8 @@ int iocb_bio_iopoll(struct kiocb *kiocb, struct io_comp_batch *iob,
 	 * point to a freshly allocated bio at this point.  If that happens
 	 * we have a few cases to consider:
 	 *
-	 *  1) the bio is beeing initialized and bi_bdev is NULL.  We can just
-	 *     simply nothing in this case
+	 *  1) the bio is being initialized and bi_bdev is NULL.  We can just
+	 *     do nothing in this case
 	 *  2) the bio points to a not poll enabled device.  bio_poll will catch
 	 *     this and return 0
 	 *  3) the bio points to a poll capable device, including but not
-- 
2.35.3


             reply	other threads:[~2024-01-14  8:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-14  8:25 Nicky Chorley [this message]
2024-01-15 14:23 ` [PATCH] block: Fix some typos 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=20240114082532.10751-1-ndchorley@gmail.com \
    --to=ndchorley@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=linux-block@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