From: patchwork-bot+netdevbpf@kernel.org
To: Beniamino Galvani <b.galvani@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, dsahern@kernel.org, gnault@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/7] net: consolidate IPv4 route lookup for UDP tunnels
Date: Mon, 16 Oct 2023 09:00:25 +0000 [thread overview]
Message-ID: <169744682508.7474.11859818002132979363.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231016071526.2958108-1-b.galvani@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Mon, 16 Oct 2023 09:15:19 +0200 you wrote:
> At the moment different UDP tunnels rely on different functions for
> IPv4 route lookup, and those functions all implement the same
> logic. Only bareudp uses the generic ip_route_output_tunnel(), while
> geneve and vxlan basically duplicate it slightly differently.
>
> This series first extends the generic lookup function so that it is
> suitable for all UDP tunnel implementations. Then, bareudp, geneve and
> vxlan are adapted to use them.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/7] ipv4: rename and move ip_route_output_tunnel()
https://git.kernel.org/netdev/net-next/c/bf3fcbf7e7a0
- [net-next,v2,2/7] ipv4: remove "proto" argument from udp_tunnel_dst_lookup()
https://git.kernel.org/netdev/net-next/c/78f3655adcb5
- [net-next,v2,3/7] ipv4: add new arguments to udp_tunnel_dst_lookup()
https://git.kernel.org/netdev/net-next/c/72fc68c6356b
- [net-next,v2,4/7] ipv4: use tunnel flow flags for tunnel route lookups
https://git.kernel.org/netdev/net-next/c/3ae983a603a4
- [net-next,v2,5/7] geneve: add dsfield helper function
https://git.kernel.org/netdev/net-next/c/60a77d11cd5d
- [net-next,v2,6/7] geneve: use generic function for tunnel IPv4 route lookup
https://git.kernel.org/netdev/net-next/c/daa2ba7ed1d1
- [net-next,v2,7/7] vxlan: use generic function for tunnel IPv4 route lookup
https://git.kernel.org/netdev/net-next/c/6f19b2c136d9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-10-16 9:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 7:15 [PATCH net-next v2 0/7] net: consolidate IPv4 route lookup for UDP tunnels Beniamino Galvani
2023-10-16 7:15 ` [PATCH net-next v2 1/7] ipv4: rename and move ip_route_output_tunnel() Beniamino Galvani
2023-10-16 7:15 ` [PATCH net-next v2 2/7] ipv4: remove "proto" argument from udp_tunnel_dst_lookup() Beniamino Galvani
2023-10-16 7:15 ` [PATCH net-next v2 3/7] ipv4: add new arguments to udp_tunnel_dst_lookup() Beniamino Galvani
2023-10-16 7:15 ` [PATCH net-next v2 4/7] ipv4: use tunnel flow flags for tunnel route lookups Beniamino Galvani
2023-10-16 7:15 ` [PATCH net-next v2 5/7] geneve: add dsfield helper function Beniamino Galvani
2023-10-16 7:15 ` [PATCH net-next v2 6/7] geneve: use generic function for tunnel IPv4 route lookup Beniamino Galvani
2023-10-16 7:15 ` [PATCH net-next v2 7/7] vxlan: " Beniamino Galvani
2023-10-16 9:00 ` 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=169744682508.7474.11859818002132979363.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=b.galvani@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=gnault@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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