diff options
author | Ben Dooks (Codethink) <ben.dooks@codethink.co.uk> | 2019-10-16 12:39:43 +0100 |
---|---|---|
committer | Marcel Holtmann <marcel@holtmann.org> | 2019-10-16 20:37:15 +0200 |
commit | 727ea61a5028f8ac96f75ab34cb1b56e63fd9227 (patch) | |
tree | 768d60e29348c52e2ea0e08526c58a154bcc6516 /drivers/bluetooth | |
parent | cef456cd354ef485f12d57000c455e83e416a2b6 (diff) | |
download | linux-727ea61a5028f8ac96f75ab34cb1b56e63fd9227.tar.gz linux-727ea61a5028f8ac96f75ab34cb1b56e63fd9227.tar.bz2 linux-727ea61a5028f8ac96f75ab34cb1b56e63fd9227.zip |
Bluetooth: missed cpu_to_le16 conversion in hci_init4_req
It looks like in hci_init4_req() the request is being
initialised from cpu-endian data but the packet is specified
to be little-endian. This causes an warning from sparse due
to __le16 to u16 conversion.
Fix this by using cpu_to_le16() on the two fields in the packet.
net/bluetooth/hci_core.c:845:27: warning: incorrect type in assignment (different base types)
net/bluetooth/hci_core.c:845:27: expected restricted __le16 [usertype] tx_len
net/bluetooth/hci_core.c:845:27: got unsigned short [usertype] le_max_tx_len
net/bluetooth/hci_core.c:846:28: warning: incorrect type in assignment (different base types)
net/bluetooth/hci_core.c:846:28: expected restricted __le16 [usertype] tx_time
net/bluetooth/hci_core.c:846:28: got unsigned short [usertype] le_max_tx_time
Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Diffstat (limited to 'drivers/bluetooth')
0 files changed, 0 insertions, 0 deletions