public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: "Asbjørn Sloth Tønnesen" <ast@fiberby.net>
To: Jens Axboe <axboe@kernel.dk>
Cc: io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] io_uring/cmd_net: split ioctl code out of io_uring_cmd_sock()
Date: Mon, 16 Feb 2026 18:31:09 +0000	[thread overview]
Message-ID: <4f0b080b-f5ea-48c3-a507-c350d3b9d2e0@fiberby.net> (raw)
In-Reply-To: <5bdb3ec3-8b25-4021-9d99-f866c4fd588c@kernel.dk>

On 2/16/26 5:46 PM, Jens Axboe wrote:
> On 2/16/26 9:03 AM, Asbjørn Sloth Tønnesen wrote:
>> io_uring_cmd_sock() originally supported two ioctl-based cmd_op
>> operations. Over time, additional operations were added with tail calls
>> to their helpers.
>>
>> This approach resulted in the new operations sharing an ioctl check
>> with the original operations.
>>
>> io_uring_cmd_sock() now supports 6 operations, so let's move the
>> implementation of the original two into their own helper, reducing
>> io_uring_cmd_sock() to a simple dispatcher.
>>
>> Signed-off-by: Asbjørn Sloth Tønnesen <ast@fiberby.net>
>> ---
>>
>> Jens, I'm used to net -> net-next taking a week, as it only happens
>> through Linus' tree.
> 
> Looks good to me - since this is just a cleanup, let's defer to 7.1.
> I'll kick that off in a week or so, at which point I'll pick this one
> up too.

Thank you, and sorry for posting during the merge window, I always
intended this for 7.1. I just took it as an invite that you merged into
for-next right after committing my fix to io_uring-7.0, given what I
wrote earlier in the RFC: "I plan to submit v1 once that patch
propagates to for-next.". I wasn't expecting it to happen that quickly.

  reply	other threads:[~2026-02-16 18:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-16 16:03 [PATCH] io_uring/cmd_net: split ioctl code out of io_uring_cmd_sock() Asbjørn Sloth Tønnesen
2026-02-16 17:46 ` Jens Axboe
2026-02-16 18:31   ` Asbjørn Sloth Tønnesen [this message]
2026-02-16 19:31     ` 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=4f0b080b-f5ea-48c3-a507-c350d3b9d2e0@fiberby.net \
    --to=ast@fiberby.net \
    --cc=axboe@kernel.dk \
    --cc=io-uring@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