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, pabeni@redhat.com,
edumazet@google.com
Subject: Re: [PATCH net 1/3] netfilter: flowtable: really fix NAT IPv6 offload
Date: Wed, 14 Dec 2022 04:00:18 +0000 [thread overview]
Message-ID: <167099041841.9337.6614576753638501976.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221213140923.154594-2-pablo@netfilter.org>
Hello:
This series was applied to netdev/net.git (master)
by Pablo Neira Ayuso <pablo@netfilter.org>:
On Tue, 13 Dec 2022 15:09:21 +0100 you wrote:
> From: Qingfang DENG <dqfext@gmail.com>
>
> The for-loop was broken from the start. It translates to:
>
> for (i = 0; i < 4; i += 4)
>
> which means the loop statement is run only once, so only the highest
> 32-bit of the IPv6 address gets mangled.
>
> [...]
Here is the summary with links:
- [net,1/3] netfilter: flowtable: really fix NAT IPv6 offload
https://git.kernel.org/netdev/net/c/5fb45f95eec6
- [net,2/3] ipvs: add a 'default' case in do_ip_vs_set_ctl()
https://git.kernel.org/netdev/net/c/ba57ee0944ff
- [net,3/3] netfilter: conntrack: document sctp timeouts
https://git.kernel.org/netdev/net/c/f9645abe4255
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-12-14 4:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 14:09 [PATCH net 0/3] Netfilter/IPVS fixes for net Pablo Neira Ayuso
2022-12-13 14:09 ` [PATCH net 1/3] netfilter: flowtable: really fix NAT IPv6 offload Pablo Neira Ayuso
2022-12-14 4:00 ` patchwork-bot+netdevbpf [this message]
2022-12-13 14:09 ` [PATCH net 2/3] ipvs: add a 'default' case in do_ip_vs_set_ctl() Pablo Neira Ayuso
2022-12-13 14:09 ` [PATCH net 3/3] netfilter: conntrack: document sctp timeouts 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=167099041841.9337.6614576753638501976.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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 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).