Bluetooth: Mesh: Use u8_t instead of bitfields for 8-bit wide values
It's cleaner to use single u8_t variables for values which require exactly 8 bits. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
This commit is contained in:
parent
7e58c5609a
commit
8488d7a9fe
1 changed files with 4 additions and 4 deletions
|
@ -226,10 +226,10 @@ struct bt_mesh_model_pub {
|
|||
u16_t addr; /* Publish Address */
|
||||
u16_t key; /* Publish AppKey Index */
|
||||
|
||||
u32_t ttl:8, /* Publish Time to Live */
|
||||
retransmit:8, /* Retransmit Count & Interval Steps */
|
||||
period:8, /* Publish Period */
|
||||
period_div:4, /* Divisor for the Period */
|
||||
u8_t ttl; /* Publish Time to Live */
|
||||
u8_t retransmit; /* Retransmit Count & Interval Steps */
|
||||
u8_t period; /* Publish Period */
|
||||
u8_t period_div:4, /* Divisor for the Period */
|
||||
cred:1; /* Friendship Credentials Flag */
|
||||
|
||||
/* Publish callback */
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue