From: Marcel Holtmann Date: Fri, 20 Mar 2015 00:22:25 +0000 (-0700) Subject: Bluetooth: Use HCI_MAX_AD_LENGTH constant instead hardcoded value X-Git-Tag: v4.1-rc1~128^2~118^2~25 X-Git-Url: https://git.karo-electronics.de/?a=commitdiff_plain;h=dc5d82a9febb28aa9126f9a864eb212317e4ede6;p=karo-tx-linux.git Bluetooth: Use HCI_MAX_AD_LENGTH constant instead hardcoded value Using the HCI_MAX_AD_LENGTH for the max advertising data and max scan response data length makes more sense than hardcoding the value. Signed-off-by: Marcel Holtmann Signed-off-by: Johan Hedberg --- diff --git a/net/bluetooth/mgmt.c b/net/bluetooth/mgmt.c index cee9bc9735af..8c771e79d67d 100644 --- a/net/bluetooth/mgmt.c +++ b/net/bluetooth/mgmt.c @@ -6312,8 +6312,8 @@ static int read_adv_features(struct sock *sk, struct hci_dev *hdev, } rp->supported_flags = cpu_to_le32(0); - rp->max_adv_data_len = 31; - rp->max_scan_rsp_len = 31; + rp->max_adv_data_len = HCI_MAX_AD_LENGTH; + rp->max_scan_rsp_len = HCI_MAX_AD_LENGTH; rp->max_instances = 0; rp->num_instances = 0;