public inbox for [email protected]
 help / color / mirror / Atom feed
From: lizetao <[email protected]>
To: Jens Axboe <[email protected]>
Cc: io-uring <[email protected]>
Subject: RE: [PATCH] io_uring: fix spelling error in uapi io_uring.h
Date: Wed, 19 Feb 2025 02:20:31 +0000	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>



> -----Original Message-----
> From: Jens Axboe <[email protected]>
> Sent: Wednesday, February 19, 2025 7:49 AM
> To: io-uring <[email protected]>
> Subject: [PATCH] io_uring: fix spelling error in uapi io_uring.h
> 
> This is obviously not that important, but when changes are synced back from
> the kernel to liburing, the codespell CI ends up erroring because of this
> misspelling. Let's just correct it and avoid this biting us again on an import.
> 
> Signed-off-by: Jens Axboe <[email protected]>
> 
> ---
> 
> diff --git a/include/uapi/linux/io_uring.h b/include/uapi/linux/io_uring.h index
> e11c82638527..050fa8eb2e8f 100644
> --- a/include/uapi/linux/io_uring.h
> +++ b/include/uapi/linux/io_uring.h
> @@ -380,7 +380,7 @@ enum io_uring_op {
>   *				result 	will be the number of buffers send,
> with
>   *				the starting buffer ID in cqe->flags as per
>   *				usual for provided buffer usage. The buffers
> - *				will be	contigious from the starting buffer ID.
> + *				will be	contiguous from the starting buffer ID.
>   */
>  #define IORING_RECVSEND_POLL_FIRST	(1U << 0)
>  #define IORING_RECV_MULTISHOT		(1U << 1)
> --
> Jens Axboe
> 

Reviewed-by: Li Zetao <[email protected]>

---
Li Zetao


      parent reply	other threads:[~2025-02-19  2:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18 23:49 [PATCH] io_uring: fix spelling error in uapi io_uring.h Jens Axboe
2025-02-19  1:21 ` David Wei
2025-02-19  2:20 ` lizetao [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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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