Thread (3 messages) flat view 3 messages, 3 authors, 2021-02-08

Re: [PATCH net-next] rxrpc: use udp tunnel APIs instead of open code in rxrpc_open_socket

From: patchwork-bot+netdevbpf@kernel.org
Date: 2021-02-08 23:21:00

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Sun,  7 Feb 2021 16:23:14 +0800 you wrote:
In rxrpc_open_socket(), now it's using sock_create_kern() and
kernel_bind() to create a udp tunnel socket, and other kernel
APIs to set up it. These code can be replaced with udp tunnel
APIs udp_sock_create() and setup_udp_tunnel_sock(), and it'll
simplify rxrpc_open_socket().

Note that with this patch, the udp tunnel socket will always
bind to a random port if transport is not provided by users,
which is suggested by David Howells, thanks!

[...]
Here is the summary with links:
  - [net-next] rxrpc: use udp tunnel APIs instead of open code in rxrpc_open_socket
    https://git.kernel.org/netdev/net-next/c/1a9b86c9fd95

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help