All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Xin Long <lucien.xin@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	dhowells@redhat.com
Subject: Re: [PATCH net-next] rxrpc: use udp tunnel APIs instead of open code in rxrpc_open_socket
Date: Mon, 08 Feb 2021 23:20:07 +0000	[thread overview]
Message-ID: <161282640727.30474.5920750020422293580.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <33e11905352da3b65354622dcd2f7d2c3c00c645.1612686194.git.lucien.xin@gmail.com>

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



      parent reply	other threads:[~2021-02-08 23:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-07  8:23 [PATCH net-next] rxrpc: use udp tunnel APIs instead of open code in rxrpc_open_socket Xin Long
2021-02-07 14:23 ` Vadim Fedorenko
2021-02-08 23:20 ` patchwork-bot+netdevbpf [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=161282640727.30474.5920750020422293580.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=kuba@kernel.org \
    --cc=lucien.xin@gmail.com \
    --cc=netdev@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.