From: patchwork-bot+netdevbpf@kernel.org
To: Anton Danilov <littlesmilingcloud@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
dsahern@kernel.org, idosch@nvidia.com, andrew+netdev@lunn.ch,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/4] vxlan: generalize and refine drop reasons
Date: Thu, 08 Oct 2026 18:00:12 +0000 [thread overview]
Message-ID: <179148241226.372666.5348049606508908025.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261005201417.906344-1-littlesmilingcloud@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
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
prev parent reply other threads:[~2026-10-08 18:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 20:14 Anton Danilov
2026-10-05 20:14 ` [PATCH net-next 1/4] vxlan: rename the drop reasons for use by other tunnels Anton Danilov
2026-10-05 20:14 ` [PATCH net-next 2/4] ip_tunnel: make __iptunnel_pull_header() return a drop reason Anton Danilov
2026-10-05 20:14 ` [PATCH net-next 3/4] vxlan: report the drop reason of __iptunnel_pull_header() Anton Danilov
2026-10-05 20:14 ` [PATCH net-next 4/4] vxlan: report a circular route as SKB_DROP_REASON_RECURSION_LIMIT Anton Danilov
2026-10-06 12:51 ` [PATCH net-next 0/4] vxlan: generalize and refine drop reasons Ido Schimmel
2026-10-08 18: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=179148241226.372666.5348049606508908025.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=littlesmilingcloud@gmail.com \
--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
all inboxes | Powered by JetHome®