From: Jens Axboe <axboe@kernel.dk>
To: Gabriel Krisman Bertazi <krisman@suse.de>
Cc: netdev@vger.kernel.org, io-uring@vger.kernel.org,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Kuniyuki Iwashima <kuniyu@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Willem de Bruijn <willemb@google.com>,
Simon Horman <horms@kernel.org>
Subject: Re: [PATCH v4 0/3] Introduce getsockname io_uring_cmd
Date: Wed, 26 Nov 2025 14:47:27 -0700 [thread overview]
Message-ID: <176419364754.144810.11021762259652723492.b4-ty@kernel.dk> (raw)
In-Reply-To: <20251125211806.2673912-1-krisman@suse.de>
On Tue, 25 Nov 2025 16:17:58 -0500, Gabriel Krisman Bertazi wrote:
> Since V3:
> - Fix passing of 'peer' in io_uring side.
> Since V2:
> - Move sockaddr_storage to do_sockname
> Since V1:
> - minor style fixes
> - Resend with (more) maintainers cc'ed
> - rebased to axboe/for-next.
> --
>
> [...]
Applied, thanks!
[1/3] socket: Unify getsockname and getpeername implementation
commit: 4677e78800bbde62a9edce0eb3b40c775ec55e0d
[2/3] socket: Split out a getsockname helper for io_uring
commit: d73c1677087391379441c0bb444c7fb4238fc6e7
[3/3] io_uring: Introduce getsockname io_uring cmd
commit: 5d24321e4c159088604512d7a5c5cf634d23e01a
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-11-26 21:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 21:17 [PATCH v4 0/3] Introduce getsockname io_uring_cmd Gabriel Krisman Bertazi
2025-11-25 21:17 ` [PATCH v4 1/3] socket: Unify getsockname and getpeername implementation Gabriel Krisman Bertazi
2025-11-25 21:18 ` [PATCH v4 2/3] socket: Split out a getsockname helper for io_uring Gabriel Krisman Bertazi
2025-11-26 0:24 ` Kuniyuki Iwashima
2025-11-25 21:18 ` [PATCH v4 3/3] io_uring: Introduce getsockname io_uring cmd Gabriel Krisman Bertazi
2025-11-26 16:51 ` Jens Axboe
2025-11-26 21:47 ` Jens Axboe [this message]
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=176419364754.144810.11021762259652723492.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=io-uring@vger.kernel.org \
--cc=krisman@suse.de \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.com \
/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