summaryrefslogtreecommitdiff
path: root/drivers/bluetooth/hci_h5.c
diff options
context:
space:
mode:
authorMarcel Holtmann <marcel@holtmann.org>2014-11-02 05:02:01 +0300
committerJohan Hedberg <johan.hedberg@intel.com>2014-11-02 11:00:53 +0300
commitb34490011d0d1a08124ffd6c4d5814ec94cd8f8f (patch)
tree96ec367c255914a90ca1831841adf36d00f4d71d /drivers/bluetooth/hci_h5.c
parent24dfa343716a493472db0555342bb88678efa444 (diff)
downloadlinux-b34490011d0d1a08124ffd6c4d5814ec94cd8f8f.tar.xz
Bluetooth: Use HCI_EV_HARDWARE_ERROR define for event payload
When constructing the event payload for the HCI_Hardware_Error event message, use the HCI_EV_HARDWARE_ERROR define. In addition rename the variables from hard_err to hw_err to clearly indicate that this is about the hardware error and not a hard error. Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Diffstat (limited to 'drivers/bluetooth/hci_h5.c')
-rw-r--r--drivers/bluetooth/hci_h5.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/bluetooth/hci_h5.c b/drivers/bluetooth/hci_h5.c
index 20bdd71559b1..bd1fe37a7993 100644
--- a/drivers/bluetooth/hci_h5.c
+++ b/drivers/bluetooth/hci_h5.c
@@ -172,7 +172,7 @@ static void h5_peer_reset(struct hci_uart *hu)
{
struct h5 *h5 = hu->priv;
struct sk_buff *skb;
- const unsigned char hard_err[] = { 0x10, 0x01, 0x00 };
+ const u8 hw_err[] = { HCI_EV_HARDWARE_ERROR, 0x01, 0x00 };
BT_ERR("Peer device has reset");
@@ -192,7 +192,7 @@ static void h5_peer_reset(struct hci_uart *hu)
return;
bt_cb(skb)->pkt_type = HCI_EVENT_PKT;
- memcpy(skb_put(skb, 3), hard_err, 3);
+ memcpy(skb_put(skb, 3), hw_err, 3);
/* Send Hardware Error to upper stack */
hci_recv_frame(hu->hdev, skb);