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
Subject: Re: [PATCH net 0/3] netfilter followup fixes for net
Date: Sat, 06 Aug 2022 02:00:15 +0000 [thread overview]
Message-ID: <165975121578.22545.985329893402476282.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220804172629.29748-1-fw@strlen.de>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel•org>:
On Thu, 4 Aug 2022 19:26:26 +0200 you wrote:
> Regressions, since 5.19:
> Fix crash when packet tracing is enabled via 'meta nftrace set 1' rule.
> Also comes with a test case.
>
> Regressions, this cycle:
> Fix Kconfig dependency for the flowtable /proc interface, we want this
> to be off by default.
>
> [...]
Here is the summary with links:
- [net,1/3] netfilter: nf_tables: fix crash when nf_trace is enabled
https://git.kernel.org/netdev/net/c/399a14ec7993
- [net,2/3] selftests: netfilter: add test case for nf trace infrastructure
https://git.kernel.org/netdev/net/c/fe9e420defab
- [net,3/3] netfilter: flowtable: fix incorrect Kconfig dependencies
https://git.kernel.org/netdev/net/c/b06ada6df9cf
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:[~2022-08-06 2:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 17:26 [PATCH net 0/3] netfilter followup fixes for net Florian Westphal
2022-08-04 17:26 ` [PATCH net 1/3] netfilter: nf_tables: fix crash when nf_trace is enabled Florian Westphal
2022-08-04 17:26 ` [PATCH net 2/3] selftests: netfilter: add test case for nf trace infrastructure Florian Westphal
2022-08-04 17:26 ` [PATCH net 3/3] netfilter: flowtable: fix incorrect Kconfig dependencies Florian Westphal
2022-08-06 2: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=165975121578.22545.985329893402476282.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=fw@strlen$(echo .)de \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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