public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Alok Tiwari <alok.a.tiwari@oracle.com>, io-uring@vger.kernel.org
Cc: alok.a.tiwarilinux@gmail.com
Subject: Re: [PATCH] io_uring: fix typos and comment wording
Date: Mon, 3 Nov 2025 11:52:11 -0700	[thread overview]
Message-ID: <a3a7f07a-50f5-4a07-9b14-4d9e41a82586@kernel.dk> (raw)
In-Reply-To: <20251103181924.476422-1-alok.a.tiwari@oracle.com>

> diff --git a/io_uring/io_uring.c b/io_uring/io_uring.c
> index 296667ba712c..59062db89ad6 100644
> --- a/io_uring/io_uring.c
> +++ b/io_uring/io_uring.c
> @@ -915,7 +915,7 @@ bool io_post_aux_cqe(struct io_ring_ctx *ctx, u64 user_data, s32 res, u32 cflags
>  }
>  
>  /*
> - * Must be called from inline task_work so we now a flush will happen later,
> + * Must be called from inline task_work so we know a flush will happen later,
>   * and obviously with ctx->uring_lock held (tw always has that).
>   */
>  void io_add_aux_cqe(struct io_ring_ctx *ctx, u64 user_data, s32 res, u32 cflags)
> @@ -1246,7 +1246,7 @@ static void io_req_local_work_add(struct io_kiocb *req, unsigned flags)
>  	BUILD_BUG_ON(IO_CQ_WAKE_FORCE <= IORING_MAX_CQ_ENTRIES);
>  
>  	/*
> -	 * We don't know how many reuqests is there in the link and whether
> +	 * We don't know how many requests is there in the link and whether
>  	 * they can even be queued lazily, fall back to non-lazy.

Should probably fix the incorrect grammar there too, if we're making
changes.

-- 
Jens Axboe

  reply	other threads:[~2025-11-03 18:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03 18:19 [PATCH] io_uring: fix typos and comment wording Alok Tiwari
2025-11-03 18:52 ` Jens Axboe [this message]
2025-11-03 19:04   ` [External] : " ALOK TIWARI

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=a3a7f07a-50f5-4a07-9b14-4d9e41a82586@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=alok.a.tiwari@oracle.com \
    --cc=alok.a.tiwarilinux@gmail.com \
    --cc=io-uring@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