public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Jonas Bonn <jonas@norrbonn.se>, io-uring@vger.kernel.org
Subject: Re: [PATCH 1/1] io_uring: fix typo in io_uring.h header
Date: Fri, 4 Apr 2025 08:38:09 -0600	[thread overview]
Message-ID: <d5192911-f98c-4b08-a507-4a1fe0100cc3@kernel.dk> (raw)
In-Reply-To: <20250404060858.539426-1-jonas@norrbonn.se>

On 4/4/25 12:08 AM, Jonas Bonn wrote:
> Comment incorrectly implies that flags are mutually exclusive; in
> reality, IORING_SETUP_TASKRUN_FLAG requires IORING_SETUP_COOP_TASKRUN.
> 
> Fixes: ef060ea9e4fd ("io_uring: add IORING_SETUP_TASKRUN_FLAG")
> Signed-off-by: Jonas Bonn <jonas@norrbonn.se>
> ---
>  include/uapi/linux/io_uring.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/uapi/linux/io_uring.h b/include/uapi/linux/io_uring.h
> index ed2beb4def3f6..e6637d693fa23 100644
> --- a/include/uapi/linux/io_uring.h
> +++ b/include/uapi/linux/io_uring.h
> @@ -183,7 +183,7 @@ enum io_uring_sqe_flags_bit {
>  /*
>   * If COOP_TASKRUN is set, get notified if task work is available for
>   * running and a kernel transition would be needed to run it. This sets
> - * IORING_SQ_TASKRUN in the sq ring flags. Not valid with COOP_TASKRUN.
> + * IORING_SQ_TASKRUN in the sq ring flags. Not valid without COOP_TASKRUN.
>   */

IORING_SETUP_TASKRUN_FLAG is not valid if either COOP_TASKRUN or
DEFER_TASKRUN are used. It's not exclusive to COOP_TASKRUN. I do agree
the comment is currently wonky, but we should mention DEFER_TASKRUN as
well when correcting it.

-- 
Jens Axboe

      reply	other threads:[~2025-04-04 14:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-04  6:08 [PATCH 1/1] io_uring: fix typo in io_uring.h header Jonas Bonn
2025-04-04 14:38 ` Jens Axboe [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=d5192911-f98c-4b08-a507-4a1fe0100cc3@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=jonas@norrbonn.se \
    /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