public inbox for [email protected]
 help / color / mirror / Atom feed
From: Ammar Faizi <[email protected]>
To: Jens Axboe <[email protected]>
Cc: Ammar Faizi <[email protected]>,
	Nicholas Rosenberg <[email protected]>,
	Michael William Jonathan <[email protected]>,
	GNU/Weeb Mailing List <[email protected]>,
	io-uring Mailing List <[email protected]>,
	Linux Kernel Mailing List <[email protected]>
Subject: [PATCH liburing v1 1/2] liburing.map: Remove `io_uring_queue_init_mem()` from v2.4
Date: Sat, 26 Aug 2023 21:17:33 +0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

io_uring_queue_init_mem() comes after 2.4 is released, so it should go
to 2.5, not 2.4.

Fixes: 7449faaf94ddfb5c25a8b6648c22016d880937ff ("setup: add support for io_uring_queue_init_mem()")
Signed-off-by: Ammar Faizi <[email protected]>
---
 src/liburing-ffi.map | 1 -
 src/liburing.map     | 1 -
 2 files changed, 2 deletions(-)

diff --git a/src/liburing-ffi.map b/src/liburing-ffi.map
index debeccde924714fc..7021227d0829335c 100644
--- a/src/liburing-ffi.map
+++ b/src/liburing-ffi.map
@@ -160,25 +160,24 @@ LIBURING_2.4 {
 		io_uring_recvmsg_cmsg_nexthdr;
 		io_uring_recvmsg_validate;
 		io_uring_prep_rw;
 		io_uring_prep_timeout;
 		io_uring_prep_linkat;
 		io_uring_prep_write_fixed;
 		io_uring_prep_poll_add;
 		io_uring_buf_ring_mask;
 		io_uring_register_restrictions;
 		io_uring_prep_write;
 		io_uring_prep_recv;
 		io_uring_prep_msg_ring_cqe_flags;
 		io_uring_prep_msg_ring_fd;
 		io_uring_prep_msg_ring_fd_alloc;
 		io_uring_prep_sendto;
-		io_uring_queue_init_mem;
 		io_uring_prep_sock_cmd;
 	local:
 		*;
 };
 
 LIBURING_2.5 {
 	global:
 		io_uring_queue_init_mem;
 } LIBURING_2.4;
diff --git a/src/liburing.map b/src/liburing.map
index 248980ea99eb05f9..8dfd5ea39378c4ae 100644
--- a/src/liburing.map
+++ b/src/liburing.map
@@ -67,22 +67,21 @@ LIBURING_2.3 {
 		io_uring_get_events;
 		io_uring_submit_and_get_events;
 } LIBURING_2.2;
 
 LIBURING_2.4 {
 	global:
 		io_uring_major_version;
 		io_uring_minor_version;
 		io_uring_check_version;
 
 		io_uring_close_ring_fd;
 		io_uring_enable_rings;
 		io_uring_register_restrictions;
 		io_uring_setup_buf_ring;
 		io_uring_free_buf_ring;
-		io_uring_queue_init_mem;
 } LIBURING_2.3;
 
 LIBURING_2.5 {
 	global:
 		io_uring_queue_init_mem;
 } LIBURING_2.4;
-- 
Ammar Faizi


  reply	other threads:[~2023-08-26 14:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-26 14:17 [PATCH liburing v1 0/2] Two small fixes for the map file Ammar Faizi
2023-08-26 14:17 ` Ammar Faizi [this message]
2023-08-26 14:17 ` [PATCH liburing v1 2/2] liburing-ffi.map: Move `io_uring_prep_sock_cmd()` to v2.5 Ammar Faizi
2023-08-28 14:11   ` Breno Leitao
2023-08-28 14:22 ` [PATCH liburing v1 0/2] Two small fixes for the map file 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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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