diff options
author | 2021-03-15 16:51:49 -0500 | |
---|---|---|
committer | 2021-03-15 20:41:58 -0700 | |
commit | 16653c16d282e768763b2e8cc78f75df8fd53992 (patch) | |
tree | 9045ff0c70cb92e0cbbc2a2a6cb9de54d03787aa /net/lapb/lapb_timer.c | |
parent | net: qualcomm: rmnet: kill RMNET_MAP_GET_*() accessor macros (diff) | |
download | wireguard-linux-16653c16d282e768763b2e8cc78f75df8fd53992.tar.xz wireguard-linux-16653c16d282e768763b2e8cc78f75df8fd53992.zip |
net: qualcomm: rmnet: use masks instead of C bit-fields
The actual layout of bits defined in C bit-fields (e.g. int foo : 3)
is implementation-defined. Structures defined in <linux/if_rmnet.h>
address this by specifying all bit-fields twice, to cover two
possible layouts.
I think this pattern is repetitive and noisy, and I find the whole
notion of compiler "bitfield endianness" to be non-intuitive.
Stop using C bit-fields for the command/data flag and the pad length
fields in the rmnet_map structure, and define a single-byte flags
field instead. Define a mask for the single-bit "command" flag,
and another mask for the encoded pad length. The content of both
fields can be accessed using a simple bitwise AND operation.
Signed-off-by: Alex Elder <elder@linaro.org>
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Reviewed-by: Alexander Duyck <alexanderduyck@fb.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/lapb/lapb_timer.c')
0 files changed, 0 insertions, 0 deletions