From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org
Subject: [PATCHSET for-next 0/4] Get rid of io_kiocb->imu
Date: Fri, 18 Oct 2024 12:38:22 -0600 [thread overview]
Message-ID: <20241018183948.464779-1-axboe@kernel.dk> (raw)
Hi,
There's really no need to keep this one in the io_kiocb, so get rid
of it.
include/linux/io_uring_types.h | 3 ---
io_uring/net.c | 29 ++++++++++++++++-------------
io_uring/rw.c | 5 +++--
io_uring/uring_cmd.c | 9 +++++----
4 files changed, 24 insertions(+), 22 deletions(-)
--
Jens Axboe
next reply other threads:[~2024-10-18 18:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 18:38 Jens Axboe [this message]
2024-10-18 18:38 ` [PATCH 1/4] io_uring/uring_cmd: get rid of using req->imu Jens Axboe
2024-10-18 19:34 ` Pavel Begunkov
2024-10-19 21:56 ` Jens Axboe
2024-10-18 18:38 ` [PATCH 2/4] io_uring/rw: " Jens Axboe
2024-10-18 18:38 ` [PATCH 3/4] io_uring/net: move send zc fixed buffer import to issue path Jens Axboe
2024-10-18 18:38 ` [PATCH 4/4] io_uring: kill 'imu' from struct io_kiocb 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=20241018183948.464779-1-axboe@kernel.dk \
--to=axboe@kernel.dk \
--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