From: Pavel Begunkov <asml.silence@gmail.com>
To: io-uring@vger.kernel.org
Cc: Jens Axboe <axboe@kernel.dk>,
asml.silence@gmail.com, linux-block@vger.kernel.org,
ming.lei@redhat.com, joshi.k@samsung.com,
linux-security-module@vger.kernel.org, selinux@vger.kernel.org,
Paul Moore <paul@paul-moore.com>
Subject: [PATCH v2 0/3] clean up io_uring cmd header structure
Date: Fri, 1 Dec 2023 00:57:34 +0000 [thread overview]
Message-ID: <cover.1701391955.git.asml.silence@gmail.com> (raw)
Looking at the zc rfc, and how we tend to stuff everything into
linux/io_uring, start splitting the file before it becomes even more
monstrous.
V2: fix up includes for security/
Add new files to MAINTAINERS
Pavel Begunkov (3):
io_uring: split out cmd api into a separate header
io_uring/cmd: inline io_uring_cmd_do_in_task_lazy
io_uring/cmd: inline io_uring_cmd_get_task
MAINTAINERS | 1 +
drivers/block/ublk_drv.c | 2 +-
drivers/nvme/host/ioctl.c | 2 +-
include/linux/io_uring.h | 89 +---------------------------------
include/linux/io_uring/cmd.h | 82 +++++++++++++++++++++++++++++++
include/linux/io_uring_types.h | 31 ++++++++++++
io_uring/io_uring.c | 1 +
io_uring/io_uring.h | 10 ----
io_uring/rw.c | 2 +-
io_uring/uring_cmd.c | 15 +-----
security/selinux/hooks.c | 2 +-
security/smack/smack_lsm.c | 2 +-
12 files changed, 122 insertions(+), 117 deletions(-)
create mode 100644 include/linux/io_uring/cmd.h
--
2.43.0
next reply other threads:[~2023-12-01 0:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 0:57 Pavel Begunkov [this message]
2023-12-01 0:57 ` [PATCH v2 1/3] io_uring: split out cmd api into a separate header Pavel Begunkov
2023-12-03 13:45 ` Ming Lei
2023-12-01 0:57 ` [PATCH v2 2/3] io_uring/cmd: inline io_uring_cmd_do_in_task_lazy Pavel Begunkov
2023-12-03 13:47 ` Ming Lei
2023-12-01 0:57 ` [PATCH v2 3/3] io_uring/cmd: inline io_uring_cmd_get_task Pavel Begunkov
2023-12-03 13:47 ` Ming Lei
2023-12-03 15:22 ` [PATCH v2 0/3] clean up io_uring cmd header structure 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=cover.1701391955.git.asml.silence@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=joshi.k@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=paul@paul-moore.com \
--cc=selinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.