public inbox for [email protected]
 help / color / mirror / Atom feed
From: David Wei <[email protected]>
To: Jens Axboe <[email protected]>, [email protected]
Cc: Pavel Begunkov <[email protected]>
Subject: Re: [PATCH liburing v1 2/3] zcrx: add basic support
Date: Tue, 18 Feb 2025 09:29:01 -0800	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 2025-02-18 09:05, Jens Axboe wrote:
> On 2/14/25 9:18 PM, David Wei wrote:
>> diff --git a/src/liburing-ffi.map b/src/liburing-ffi.map
>> index 83593a33826a..cedc71383547 100644
>> --- a/src/liburing-ffi.map
>> +++ b/src/liburing-ffi.map
>> @@ -222,6 +222,7 @@ LIBURING_2.9 {
>>  		io_uring_register_wait_reg;
>>  		io_uring_submit_and_wait_reg;
>>  		io_uring_clone_buffers_offset;
>> +		io_uring_register_ifq;
>>  		io_uring_register_region;
>>  		io_uring_sqe_set_buf_group;
>>  } LIBURING_2.8;
>> diff --git a/src/liburing.map b/src/liburing.map
>> index 9f7b21171218..81dd6ab9b8cc 100644
>> --- a/src/liburing.map
>> +++ b/src/liburing.map
>> @@ -109,5 +109,6 @@ LIBURING_2.9 {
>>  		io_uring_register_wait_reg;
>>  		io_uring_submit_and_wait_reg;
>>  		io_uring_clone_buffers_offset;
>> +		io_uring_register_ifq;
>>  		io_uring_register_region;
>>  } LIBURING_2.8;
> 
> This isn't right - 2.9 has already been released, you can't add new
> symbols to an existing release. I usually bump the version post release,
> but looks like I didn't this time - corrected now, with a new empty
> section for 2.10 symbols as well where these should go.
> 

Thanks, I'll rebase and add to 2.10.

  reply	other threads:[~2025-02-18 17:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-15  4:18 [PATCH liburing v1 0/3] add basic zero copy receive support David Wei
2025-02-15  4:18 ` [PATCH liburing v1 1/3] zcrx: sync kernel headers David Wei
2025-02-18 17:04   ` Jens Axboe
2025-02-18 17:28     ` David Wei
2025-02-15  4:18 ` [PATCH liburing v1 2/3] zcrx: add basic support David Wei
2025-02-18 17:05   ` Jens Axboe
2025-02-18 17:29     ` David Wei [this message]
2025-02-15  4:18 ` [PATCH liburing v1 3/3] zcrx: add unit test David Wei
2025-02-18 17:01 ` [PATCH liburing v1 0/3] add basic zero copy receive support Jens Axboe
2025-02-18 17:30   ` David Wei
2025-02-18 17:31     ` 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] \
    /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