From: patchwork-bot+netdevbpf@kernel.org
To: Alexander Lobakin <alobakin@pm.me>
Cc: davem@davemloft.net, kuba@kernel.org, jakub@cloudflare.com,
ast@kernel.org, andriin@fb.com, vladimir.oltean@nxp.com,
dcaratti@redhat.com, gnault@redhat.com, wenxu@ucloud.cn,
eranbe@nvidia.com, mcroce@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] flow_dissector: fix byteorder of dissected ICMP ID
Date: Sun, 14 Mar 2021 22:40:08 +0000 [thread overview]
Message-ID: <161576160891.5046.7644806242984033083.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210312200834.370667-1-alobakin@pm.me>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Fri, 12 Mar 2021 20:08:57 +0000 you wrote:
> flow_dissector_key_icmp::id is of type u16 (CPU byteorder),
> ICMP header has its ID field in network byteorder obviously.
> Sparse says:
>
> net/core/flow_dissector.c:178:43: warning: restricted __be16 degrades to integer
>
> Convert ID value to CPU byteorder when storing it into
> flow_dissector_key_icmp.
>
> [...]
Here is the summary with links:
- [net] flow_dissector: fix byteorder of dissected ICMP ID
https://git.kernel.org/netdev/net/c/a25f82228542
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:[~2021-03-14 22:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 20:08 [PATCH net] flow_dissector: fix byteorder of dissected ICMP ID Alexander Lobakin
2021-03-14 20:21 ` Jakub Sitnicki
2021-03-14 20:44 ` Vladimir Oltean
2021-03-14 21:31 ` David Miller
2021-03-14 22:40 ` 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=161576160891.5046.7644806242984033083.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alobakin@pm.me \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=eranbe@nvidia.com \
--cc=gnault@redhat.com \
--cc=jakub@cloudflare.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcroce@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=vladimir.oltean@nxp.com \
--cc=wenxu@ucloud.cn \
/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).