From: patchwork-bot+netdevbpf@kernel.org
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, davem@davemloft.net,
netdev@vger.kernel.org, kuba@kernel.org
Subject: Re: [PATCH net 1/8] netfilter: Remove flowtable relics
Date: Fri, 28 Jan 2022 03:00:12 +0000 [thread overview]
Message-ID: <164333881243.25446.10078573263507923141.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220127235235.656931-2-pablo@netfilter.org>
Hello:
This series was applied to netdev/net.git (master)
by Pablo Neira Ayuso <pablo@netfilter.org>:
On Fri, 28 Jan 2022 00:52:28 +0100 you wrote:
> From: Geert Uytterhoeven <geert@linux-m68k.org>
>
> NF_FLOW_TABLE_IPV4 and NF_FLOW_TABLE_IPV6 are invisble, selected by
> nothing (so they can no longer be enabled), and their last real users
> have been removed (nf_flow_table_ipv6.c is empty).
>
> Clean up the leftovers.
>
> [...]
Here is the summary with links:
- [net,1/8] netfilter: Remove flowtable relics
https://git.kernel.org/netdev/net/c/7355bfe0e0cc
- [net,2/8] netfilter: nft_ct: fix use after free when attaching zone template
https://git.kernel.org/netdev/net/c/34243b9ec856
- [net,3/8] selftests: netfilter: reduce zone stress test running time
https://git.kernel.org/netdev/net/c/c858620d2ae3
- [net,4/8] selftests: netfilter: check stateless nat udp checksum fixup
https://git.kernel.org/netdev/net/c/aad51ca71ad8
- [net,5/8] netfilter: nft_reject_bridge: Fix for missing reply from prerouting
https://git.kernel.org/netdev/net/c/aeac4554eb54
- [net,6/8] netfilter: nft_byteorder: track register operations
https://git.kernel.org/netdev/net/c/f459bfd4b979
- [net,7/8] selftests: nft_concat_range: add test for reload with no element add/del
https://git.kernel.org/netdev/net/c/eda0cf1202ac
- [net,8/8] netfilter: nf_tables: remove assignment with no effect in chain blob builder
https://git.kernel.org/netdev/net/c/b07f41373254
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-01-28 3:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 23:52 [PATCH net 0/8] Netfilter fixes for net Pablo Neira Ayuso
2022-01-27 23:52 ` [PATCH net 1/8] netfilter: Remove flowtable relics Pablo Neira Ayuso
2022-01-28 3:00 ` patchwork-bot+netdevbpf [this message]
2022-01-27 23:52 ` [PATCH net 2/8] netfilter: nft_ct: fix use after free when attaching zone template Pablo Neira Ayuso
2022-01-27 23:52 ` [PATCH net 3/8] selftests: netfilter: reduce zone stress test running time Pablo Neira Ayuso
2022-01-27 23:52 ` [PATCH net 4/8] selftests: netfilter: check stateless nat udp checksum fixup Pablo Neira Ayuso
2022-01-27 23:52 ` [PATCH net 5/8] netfilter: nft_reject_bridge: Fix for missing reply from prerouting Pablo Neira Ayuso
2022-01-27 23:52 ` [PATCH net 6/8] netfilter: nft_byteorder: track register operations Pablo Neira Ayuso
2022-01-27 23:52 ` [PATCH net 7/8] selftests: nft_concat_range: add test for reload with no element add/del Pablo Neira Ayuso
2022-01-27 23:52 ` [PATCH net 8/8] netfilter: nf_tables: remove assignment with no effect in chain blob builder Pablo Neira Ayuso
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=164333881243.25446.10078573263507923141.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).