Commit f5fcca89 authored by Vladimir Oltean's avatar Vladimir Oltean Committed by David S. Miller

net: bridge: declare br_vlan_tunnel_lookup argument tunnel_id as __be64

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 *.

Therefore, there is no functional change associated with this patch,
just one to silence "make W=1" builds.
Signed-off-by: default avatarVladimir Oltean <vladimir.oltean@nxp.com>
Acked-by: default avatarNikolay Aleksandrov <nikolay@nvidia.com>
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
parent c3c3791c
...@@ -35,7 +35,7 @@ static const struct rhashtable_params br_vlan_tunnel_rht_params = { ...@@ -35,7 +35,7 @@ static const struct rhashtable_params br_vlan_tunnel_rht_params = {
}; };
static struct net_bridge_vlan *br_vlan_tunnel_lookup(struct rhashtable *tbl, static struct net_bridge_vlan *br_vlan_tunnel_lookup(struct rhashtable *tbl,
u64 tunnel_id) __be64 tunnel_id)
{ {
return rhashtable_lookup_fast(tbl, &tunnel_id, return rhashtable_lookup_fast(tbl, &tunnel_id,
br_vlan_tunnel_rht_params); br_vlan_tunnel_rht_params);
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment