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-next 1/8] netfilter: ecache: remove one indent level
Date: Mon, 30 Aug 2021 10:00:06 +0000 [thread overview]
Message-ID: <163031760688.27483.14106552894924526730.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210830093852.21654-2-pablo@netfilter.org>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Mon, 30 Aug 2021 11:38:45 +0200 you wrote:
> From: Florian Westphal <fw@strlen.de>
>
> nf_conntrack_eventmask_report and nf_ct_deliver_cached_events shared
> most of their code. This unifies the layout by changing
>
> if (nf_ct_is_confirmed(ct)) {
> foo
> }
>
> [...]
Here is the summary with links:
- [net-next,1/8] netfilter: ecache: remove one indent level
https://git.kernel.org/netdev/net-next/c/478374a3c15f
- [net-next,2/8] netfilter: ecache: remove another indent level
https://git.kernel.org/netdev/net-next/c/9291f0902d0c
- [net-next,3/8] netfilter: ecache: add common helper for nf_conntrack_eventmask_report
https://git.kernel.org/netdev/net-next/c/b3afdc175863
- [net-next,4/8] netfilter: ecache: prepare for event notifier merge
https://git.kernel.org/netdev/net-next/c/b86c0e6429da
- [net-next,5/8] netfilter: ecache: remove nf_exp_event_notifier structure
https://git.kernel.org/netdev/net-next/c/bd1431db0b81
- [net-next,6/8] netfilter: ctnetlink: missing counters and timestamp in nfnetlink_{log,queue}
https://git.kernel.org/netdev/net-next/c/6c89dac5b985
- [net-next,7/8] netfilter: x_tables: handle xt_register_template() returning an error value
https://git.kernel.org/netdev/net-next/c/7bc416f14716
- [net-next,8/8] netfilter: add netfilter hooks to SRv6 data plane
https://git.kernel.org/netdev/net-next/c/7a3f5b0de364
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:[~2021-08-30 10:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 9:38 [PATCH net-next 0/8] Netfilter updates for net-next Pablo Neira Ayuso
2021-08-30 9:38 ` [PATCH net-next 1/8] netfilter: ecache: remove one indent level Pablo Neira Ayuso
2021-08-30 10:00 ` patchwork-bot+netdevbpf [this message]
2021-08-30 9:38 ` [PATCH net-next 2/8] netfilter: ecache: remove another " Pablo Neira Ayuso
2021-08-30 9:38 ` [PATCH net-next 3/8] netfilter: ecache: add common helper for nf_conntrack_eventmask_report Pablo Neira Ayuso
2021-08-30 9:38 ` [PATCH net-next 4/8] netfilter: ecache: prepare for event notifier merge Pablo Neira Ayuso
2021-08-30 9:38 ` [PATCH net-next 5/8] netfilter: ecache: remove nf_exp_event_notifier structure Pablo Neira Ayuso
2021-08-30 9:38 ` [PATCH net-next 6/8] netfilter: ctnetlink: missing counters and timestamp in nfnetlink_{log,queue} Pablo Neira Ayuso
2021-08-30 9:38 ` [PATCH net-next 7/8] netfilter: x_tables: handle xt_register_template() returning an error value Pablo Neira Ayuso
2021-08-30 9:38 ` [PATCH net-next 8/8] netfilter: add netfilter hooks to SRv6 data plane 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=163031760688.27483.14106552894924526730.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 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.