From: Jens Axboe <axboe@kernel.dk>
To: Gabriel Krisman Bertazi <krisman@suse.de>
Cc: io-uring@vger.kernel.org, csander@purestorage.com
Subject: Re: [PATCH liburing v2 0/4] liburing: getsockname support
Date: Tue, 2 Dec 2025 08:16:42 -0700 [thread overview]
Message-ID: <7dbc9882-0f14-4e0d-9d9c-64307baa5332@kernel.dk> (raw)
In-Reply-To: <20251125212715.2679630-1-krisman@suse.de>
On 11/25/25 2:27 PM, Gabriel Krisman Bertazi wrote:
> Since V1:
> - bind-test.t: use client socket used when doing a getpeername
> - Use the new io_uring_prep_uring_cmd to define prep_cmc_getsockname
Can you send a v3 please, with the things highlighted in my review
sorted? I want to release liburing 2.13 before the holidays, and since
we'll have the kernel support for this in the 6.19 kernel, we really
should have the liburing support in place too.
--
Jens Axboe
next prev parent reply other threads:[~2025-12-02 15:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 21:27 [PATCH liburing v2 0/4] liburing: getsockname support Gabriel Krisman Bertazi
2025-11-25 21:27 ` [PATCH liburing v2 1/4] liburing: Introduce getsockname operation Gabriel Krisman Bertazi
2025-11-25 21:27 ` [PATCH liburing v2 2/4] test/bind-listen.t: Use ephemeral port Gabriel Krisman Bertazi
2025-11-26 20:49 ` Jens Axboe
2025-12-02 23:37 ` Gabriel Krisman Bertazi
2025-12-03 2:49 ` Jens Axboe
2025-11-25 21:27 ` [PATCH liburing v2 3/4] bind-listen.t: Add tests for getsockname Gabriel Krisman Bertazi
2025-11-26 20:58 ` Jens Axboe
2025-11-25 21:27 ` [PATCH liburing v2 4/4] man/io_uring_prep_getsockname.3: Add man page Gabriel Krisman Bertazi
2025-11-26 20:54 ` Jens Axboe
2025-12-02 15:16 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-20 22:13 [PATCH liburing v2 0/4] liburing: getsockname support Gabriel Krisman Bertazi
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=7dbc9882-0f14-4e0d-9d9c-64307baa5332@kernel.dk \
--to=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=io-uring@vger.kernel.org \
--cc=krisman@suse.de \
/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