Hi Ben,

> 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 <[email protected]>
> ---
> Cc: Marcel Holtmann <[email protected]>
> Cc: Johan Hedberg <[email protected]>
> Cc: "David S. Miller" <[email protected]>
> Cc: [email protected]
> Cc: [email protected]
> Cc: [email protected]
> ---
> net/bluetooth/hci_core.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)

patch has been applied to bluetooth-next tree.

Regards

Marcel

Reply via email to