From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <olteanv@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
roopa@nvidia.com, nikolay@nvidia.com, vladimir.oltean@nxp.com
Subject: Re: [PATCH net-next] net: bridge: declare br_vlan_tunnel_lookup argument tunnel_id as __be64
Date: Mon, 22 Mar 2021 20:20:08 +0000 [thread overview]
Message-ID: <161644440812.26518.17110056440678618651.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210322103819.3723179-1-olteanv@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Mon, 22 Mar 2021 12:38:19 +0200 you wrote:
> From: Vladimir Oltean <vladimir.oltean@nxp.com>
>
> The only caller of br_vlan_tunnel_lookup, br_handle_ingress_vlan_tunnel,
> extracts the tunnel_id from struct ip_tunnel_info::struct ip_tunnel_key::
> tun_id which is a __be64 value.
>
> The exact endianness does not seem to matter, because the tunnel id is
> just used as a lookup key for the VLAN group's tunnel hash table, and
> the value is not interpreted directly per se. Moreover,
> rhashtable_lookup_fast treats the key argument as a const void *.
>
> [...]
Here is the summary with links:
- [net-next] net: bridge: declare br_vlan_tunnel_lookup argument tunnel_id as __be64
https://git.kernel.org/netdev/net-next/c/f5fcca89f59c
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-22 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 10:38 [PATCH net-next] net: bridge: declare br_vlan_tunnel_lookup argument tunnel_id as __be64 Vladimir Oltean
2021-03-22 10:42 ` Nikolay Aleksandrov
2021-03-22 20:20 ` 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=161644440812.26518.17110056440678618651.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=nikolay@nvidia.com \
--cc=olteanv@gmail.com \
--cc=roopa@nvidia.com \
--cc=vladimir.oltean@nxp.com \
/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