From: Haiyue Wang <haiyuewa@163.com>
To: io-uring@vger.kernel.org
Cc: Haiyue Wang <haiyuewa@163.com>
Subject: [PATCH liburing v1] register: Remove old API io_uring_register_wait_reg
Date: Sat, 17 May 2025 22:07:21 +0800 [thread overview]
Message-ID: <20250517140725.24052-1-haiyuewa@163.com> (raw)
The commit b38747291d50 ("queue: break reg wait setup") just left this
API definition with always "-EINVAL" result for building test.
And new API 'io_uring_submit_and_wait_reg' has been implemented.
Signed-off-by: Haiyue Wang <haiyuewa@163.com>
---
src/include/liburing.h | 2 --
src/liburing-ffi.map | 1 -
src/liburing.map | 1 -
src/register.c | 6 ------
4 files changed, 10 deletions(-)
diff --git a/src/include/liburing.h b/src/include/liburing.h
index a953a6f..8dfbf31 100644
--- a/src/include/liburing.h
+++ b/src/include/liburing.h
@@ -210,8 +210,6 @@ int io_uring_submit_and_wait_reg(struct io_uring *ring,
struct io_uring_cqe **cqe_ptr, unsigned wait_nr,
int reg_index);
-int io_uring_register_wait_reg(struct io_uring *ring,
- struct io_uring_reg_wait *reg, int nr);
int io_uring_resize_rings(struct io_uring *ring, struct io_uring_params *p);
int io_uring_clone_buffers_offset(struct io_uring *dst, struct io_uring *src,
unsigned int dst_off, unsigned int src_off,
diff --git a/src/liburing-ffi.map b/src/liburing-ffi.map
index 7f6d4af..662840d 100644
--- a/src/liburing-ffi.map
+++ b/src/liburing-ffi.map
@@ -219,7 +219,6 @@ LIBURING_2.8 {
LIBURING_2.9 {
global:
io_uring_resize_rings;
- io_uring_register_wait_reg;
io_uring_submit_and_wait_reg;
io_uring_clone_buffers_offset;
io_uring_register_region;
diff --git a/src/liburing.map b/src/liburing.map
index c946115..84114d2 100644
--- a/src/liburing.map
+++ b/src/liburing.map
@@ -106,7 +106,6 @@ LIBURING_2.8 {
LIBURING_2.9 {
io_uring_resize_rings;
- io_uring_register_wait_reg;
io_uring_submit_and_wait_reg;
io_uring_clone_buffers_offset;
io_uring_register_region;
diff --git a/src/register.c b/src/register.c
index 51667d8..68944ed 100644
--- a/src/register.c
+++ b/src/register.c
@@ -471,12 +471,6 @@ out:
return ret;
}
-int io_uring_register_wait_reg(struct io_uring *ring,
- struct io_uring_reg_wait *reg, int nr)
-{
- return -EINVAL;
-}
-
int io_uring_register_region(struct io_uring *ring,
struct io_uring_mem_region_reg *reg)
{
--
2.49.0
next reply other threads:[~2025-05-17 14:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-17 14:07 Haiyue Wang [this message]
2025-05-17 14:20 ` [PATCH liburing v1] register: Remove old API io_uring_register_wait_reg Jens Axboe
2025-05-17 14:31 ` Haiyue Wang
2025-05-17 14:33 ` Jens Axboe
2025-05-17 14:36 ` Haiyue Wang
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=20250517140725.24052-1-haiyuewa@163.com \
--to=haiyuewa@163.com \
--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