From: patchwork-bot+netdevbpf@kernel.org
To: Ilya Maximets <i.maximets@ovn.org>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, aconole@redhat.com,
echaudro@redhat.com, dsahern@kernel.org, idosch@nvidia.com,
shuah@kernel.org, kuniyu@google.com, razor@blackwall.org,
fmancera@suse.de, atenart@kernel.org,
linux-kernel@vger.kernel.org, dev@openvswitch.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next 0/6] openvswitch: remove support for legacy tunnel ports
Date: Thu, 06 Aug 2026 13:20:18 +0000 [thread overview]
Message-ID: <178602241884.840277.8360130594768086781.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260804182049.2289754-1-i.maximets@ovn.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 4 Aug 2026 20:20:34 +0200 you wrote:
> ovs-vswitchd doesn't use OVS_VPORT_TYPE_GRE/VXLAN/GENEVE with the
> Linux kernel module since adding support for standard tunnel devices
> with COLLECT_METADATA back in 2017. The code to use them was only
> activated as a fallback for old kernels, so not used in practice. And
> it is now fully removed in the upcoming OVS 4.0 release.
>
> Modern way to use tunnels with OVS is to create standard tunnel ports
> with RTM_NEWLINK + COLLECT_METADATA and add them as OVS_VPORT_TYPE_NETDEV.
>
> [...]
Here is the summary with links:
- [net-next,1/6] openvswitch: remove support for legacy tunnel types
https://git.kernel.org/netdev/net-next/c/d26dcf73a8f1
- [net-next,2/6] openvswitch: vport: remove infrastructure for vport options
https://git.kernel.org/netdev/net-next/c/38aecd1a1973
- [net-next,3/6] openvswitch: vport: remove infrastructure for separate modules
https://git.kernel.org/netdev/net-next/c/2425eba0f822
- [net-next,4/6] net: geneve: remove unused geneve_dev_create_fb
https://git.kernel.org/netdev/net-next/c/e5ba33295201
- [net-next,5/6] net: gre: remove unused gretap_fb_dev_create
https://git.kernel.org/netdev/net-next/c/9646825a51c4
- [net-next,6/6] net: vxlan: remove unused vxlan_dev_create
https://git.kernel.org/netdev/net-next/c/a5ae637f863d
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-08-06 13:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 18:20 [PATCH net-next 0/6] openvswitch: remove support for legacy tunnel ports Ilya Maximets
2026-08-04 18:20 ` [PATCH net-next 1/6] openvswitch: remove support for legacy tunnel types Ilya Maximets
2026-08-04 18:20 ` [PATCH net-next 2/6] openvswitch: vport: remove infrastructure for vport options Ilya Maximets
2026-08-04 18:20 ` [PATCH net-next 3/6] openvswitch: vport: remove infrastructure for separate modules Ilya Maximets
2026-08-04 18:20 ` [PATCH net-next 4/6] net: geneve: remove unused geneve_dev_create_fb Ilya Maximets
2026-08-04 18:20 ` [PATCH net-next 5/6] net: gre: remove unused gretap_fb_dev_create Ilya Maximets
2026-08-04 18:20 ` [PATCH net-next 6/6] net: vxlan: remove unused vxlan_dev_create Ilya Maximets
2026-08-06 11:03 ` [PATCH net-next 0/6] openvswitch: remove support for legacy tunnel ports Paolo Abeni
2026-08-06 13: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=178602241884.840277.8360130594768086781.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aconole@redhat.com \
--cc=andrew+netdev@lunn.ch \
--cc=atenart@kernel.org \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=dsahern@kernel.org \
--cc=echaudro@redhat.com \
--cc=edumazet@google.com \
--cc=fmancera@suse.de \
--cc=horms@kernel.org \
--cc=i.maximets@ovn.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=shuah@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox