From: Jens Axboe <axboe@kernel.dk>
To: Caleb Sander Mateos <csander@purestorage.com>
Cc: io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] io_uring/uring_cmd: add io_uring_cmd_tw_t type alias
Date: Tue, 02 Sep 2025 19:21:43 -0600 [thread overview]
Message-ID: <175686250399.108754.12103527747945353586.b4-ty@kernel.dk> (raw)
In-Reply-To: <20250902160657.1726828-1-csander@purestorage.com>
On Tue, 02 Sep 2025 10:06:56 -0600, Caleb Sander Mateos wrote:
> Introduce a function pointer type alias io_uring_cmd_tw_t for the
> uring_cmd task work callback. This avoids repeating the signature in
> several places. Also name both arguments to the callback to clarify what
> they represent.
>
>
Applied, thanks!
[1/1] io_uring/uring_cmd: add io_uring_cmd_tw_t type alias
commit: df3a7762ee24ba6a33d4215244e329ca300f4819
Best regards,
--
Jens Axboe
next prev parent reply other threads:[~2025-09-03 1:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 16:06 [PATCH] io_uring/uring_cmd: add io_uring_cmd_tw_t type alias Caleb Sander Mateos
2025-09-02 17:46 ` Keith Busch
2025-09-03 1:21 ` Jens Axboe [this message]
2025-09-07 12:33 ` Klara Modin
2025-09-08 14:20 ` 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=175686250399.108754.12103527747945353586.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=csander@purestorage.com \
--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