Commit dc5d82a9 authored Mar 19, 2015 by Marcel Holtmann Committed by Johan Hedberg Mar 20, 2015

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>

parent e7844ee5

net/bluetooth/mgmt.c

+2 −2

Original line number	Diff line number	Diff line
		@@ -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;

Admin message