On 1/29/21 3:56 AM, Vladimir Oltean wrote:
> The flow steering struct ethtool_flow_ext::data field is __be32, so when
> the CFP code needs to check the VLAN egress tagging attribute in bit 0,
> it does this in CPU native endianness. So logically, the endianness
> conversion is set up the other way around, although in practice the same
> result is produced.
> 
> Gets rid of build warning:
> 
> warning: cast from restricted __be32
> warning: incorrect type in argument 1 (different base types)
>    expected unsigned int [usertype] val
>    got restricted __be32
> warning: cast from restricted __be32
> warning: cast from restricted __be32
> warning: cast from restricted __be32
> warning: cast from restricted __be32
> warning: restricted __be32 degrades to integer
> 
> Signed-off-by: Vladimir Oltean <olte...@gmail.com>

Acked-by: Florian Fainelli <f.faine...@gmail.com>
-- 
Florian

Reply via email to