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-next 1/6] netfilter: nft_payload: use __be16 to store gre version
Date: Wed, 16 Nov 2022 05:00:19 +0000 [thread overview]
Message-ID: <166857481974.8148.14898836218257392922.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221115095922.139954-2-pablo@netfilter.org>
Hello:
This series was applied to netdev/net-next.git (master)
by Pablo Neira Ayuso <pablo@netfilter.org>:
On Tue, 15 Nov 2022 10:59:17 +0100 you wrote:
> GRE_VERSION and GRE_VERSION0 are expressed in network byte order,
> use __be16. Uncovered by sparse:
>
> net/netfilter/nft_payload.c:112:25: warning: incorrect type in assignment (different base types)
> net/netfilter/nft_payload.c:112:25: expected unsigned int [usertype] version
> net/netfilter/nft_payload.c:112:25: got restricted __be16
> net/netfilter/nft_payload.c:114:22: warning: restricted __be16 degrades to integer
>
> [...]
Here is the summary with links:
- [net-next,1/6] netfilter: nft_payload: use __be16 to store gre version
https://git.kernel.org/netdev/net-next/c/66394126bf20
- [net-next,2/6] netfilter: nft_inner: fix return value check in nft_inner_parse_l2l3()
https://git.kernel.org/netdev/net-next/c/7394c2dd62de
- [net-next,3/6] netfilter: nf_tables: Extend nft_expr_ops::dump callback parameters
https://git.kernel.org/netdev/net-next/c/7d34aa3e03b6
- [net-next,4/6] netfilter: nf_tables: Introduce NFT_MSG_GETRULE_RESET
https://git.kernel.org/netdev/net-next/c/8daa8fde3fc3
- [net-next,5/6] netfilter: rpfilter/fib: clean up some inconsistent indenting
https://git.kernel.org/netdev/net-next/c/971095c6fa4a
- [net-next,6/6] netfilter: conntrack: use siphash_4u64
https://git.kernel.org/netdev/net-next/c/d2c806abcf0b
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-11-16 5:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 9:59 [PATCH net-next,v2 0/6] Netfilter updates for net-next Pablo Neira Ayuso
2022-11-15 9:59 ` [PATCH net-next 1/6] netfilter: nft_payload: use __be16 to store gre version Pablo Neira Ayuso
2022-11-16 5:00 ` patchwork-bot+netdevbpf [this message]
2022-11-15 9:59 ` [PATCH net-next 2/6] netfilter: nft_inner: fix return value check in nft_inner_parse_l2l3() Pablo Neira Ayuso
2022-11-15 9:59 ` [PATCH net-next 3/6] netfilter: nf_tables: Extend nft_expr_ops::dump callback parameters Pablo Neira Ayuso
2022-11-15 9:59 ` [PATCH net-next 4/6] netfilter: nf_tables: Introduce NFT_MSG_GETRULE_RESET Pablo Neira Ayuso
2022-11-15 9:59 ` [PATCH net-next 5/6] netfilter: rpfilter/fib: clean up some inconsistent indenting Pablo Neira Ayuso
2022-11-15 9:59 ` [PATCH net-next 6/6] netfilter: conntrack: use siphash_4u64 Pablo Neira Ayuso
-- strict thread matches above, loose matches on Subject: below --
2022-11-14 10:41 [PATCH net-next 0/6] Netfilter updates for net-next Pablo Neira Ayuso
2022-11-14 10:41 ` [PATCH net-next 1/6] netfilter: nft_payload: use __be16 to store gre version 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=166857481974.8148.14898836218257392922.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).