From: patchwork-bot+netdevbpf@kernel.org
To: Florian Westphal <fw@strlen.de>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org,
netfilter-devel@vger.kernel.org, pablo@netfilter.org
Subject: Re: [GIT PULL v2 net-next] netfilter: updates for net-next
Date: Thu, 09 Apr 2026 02:10:27 +0000 [thread overview]
Message-ID: <177570062729.956260.4386026678361572614.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260408060419.25258-1-fw@strlen.de>
Hello:
This pull request was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 8 Apr 2026 08:04:19 +0200 you wrote:
> No changes since v1, I only dropped the last patch (13/13). This is also
> why I am not resending the individual patches again.
>
> The following PR contains Netfilter updates for *net-next*:
>
> 1) Fix ancient sparse warnings in nf conntrack nat modules, from
> Sun Jian.
> 2) Fix typo in enum description, from Jelle van der Waa.
> 3) remove redundant refetch of netns pointer in nf_conntrack_sip.
> 4) add a deprecation warning for dccp match.
> We can extend the deadline later if needed, but plan atm is to
> remove the feature.
> 5) remove nf_conntrack_h323 debug code that can read out-of-bounds
> with malformed messages. This code was commented out, but better
> remove this.
> 6+7) add more netlink policy validations in netfilter.
> This could theoretically cause issues when a client sends e.g.
> unsupported feature flags that were previously ignored, so we
> may have to relax some changes. For now, try to be stricter and
> reject upfront.
> 8+9) minor code cleanup in nft_set_pipapo (an nftables set backend).
> 10) Add nftables matching support fro double-tagged vlan and pppoe
> frames, from Pablo Neira Ayuso.
> 11) Fix up indentation of debug messages in nf_conntrack_h323 conntrack
> helper, from David Laight.
> 12) Add a helper to iterate to next flow action and bail out if the
> maximum number of actions is reached, also from Pablo.
>
> [...]
Here is the summary with links:
- [GIT,PULL,v2,net-next] netfilter: updates for net-next
https://git.kernel.org/netdev/net-next/c/1795654f0005
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-04-09 2:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 6:04 [GIT PULL v2 net-next] netfilter: updates for net-next Florian Westphal
2026-04-09 2:10 ` 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=177570062729.956260.4386026678361572614.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.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.