diff options
| author | Marcel Holtmann <marcel@holtmann.org> | 2015-03-20 00:22:25 (GMT) |
|---|---|---|
| committer | Johan Hedberg <johan.hedberg@intel.com> | 2015-03-20 12:08:32 (GMT) |
| commit | dc5d82a9febb28aa9126f9a864eb212317e4ede6 (patch) | |
| tree | 49340b7dbc16bd81e3d3df1d4433edb28b7ccdda | |
| parent | e7844ee599c3eb944c3bd0092d715ca86e76a1f3 (diff) | |
| download | linux-dc5d82a9febb28aa9126f9a864eb212317e4ede6.tar.xz | |
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 <marcel@holtmann.org>
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
| -rw-r--r-- | net/bluetooth/mgmt.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/net/bluetooth/mgmt.c b/net/bluetooth/mgmt.c index cee9bc9..8c771e7 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; |