Re: [PATCH net-next 0/4] vxlan: generalize and refine drop reasons

[patchwork-bot+netdevbpf]

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@xxxxxxxxxx>:

On Mon,  5 Oct 2026 23:14:13 +0300 you wrote:
> This series makes two vxlan drop reasons generic, so that other tunnels
> can report the same conditions with them, and makes the reasons vxlan
> reports for two other failures more precise.
> 
> Patch 1 renames VXLAN_INVALID_HDR and VXLAN_VNI_NOT_FOUND to
> TUNNEL_INVALID_HDR and TUNNEL_NOT_FOUND. Their values stay the same;
> the names vxlan drops are reported with change.
> 
> [...]

Here is the summary with links:
  - [net-next,1/4] vxlan: rename the drop reasons for use by other tunnels
    https://git.kernel.org/netdev/net-next/c/7629d6db839f
  - [net-next,2/4] ip_tunnel: make __iptunnel_pull_header() return a drop reason
    https://git.kernel.org/netdev/net-next/c/6c0509aa8900
  - [net-next,3/4] vxlan: report the drop reason of __iptunnel_pull_header()
    https://git.kernel.org/netdev/net-next/c/0518c33e1d7e
  - [net-next,4/4] vxlan: report a circular route as SKB_DROP_REASON_RECURSION_LIMIT
    https://git.kernel.org/netdev/net-next/c/d476bb7c0efd

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