Searched hist:"242 c0ebd3730334c43b9c04eeec40d8dd5c3a26e" (Results 1 – 5 of 5) sorted by relevance
/openbmc/linux/net/bluetooth/ |
H A D | hci_request.c | diff 242c0ebd3730334c43b9c04eeec40d8dd5c3a26e Sun Oct 25 16:45:53 CDT 2015 Marcel Holtmann <marcel@holtmann.org> Bluetooth: Rename bt_cb()->req into bt_cb()->hci
The SKB context buffer for HCI request is really not just for requests, information in their are preserved for the whole HCI layer. So it makes more sense to actually rename it into bt_cb()->hci and also call it then struct hci_ctrl.
In addition that allows moving the decoded opcode for outgoing packets into that struct. So far it was just consuming valuable space from the main shared items. And opcode are not valid for L2CAP packets.
Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
|
H A D | hci_sock.c | diff 242c0ebd3730334c43b9c04eeec40d8dd5c3a26e Sun Oct 25 16:45:53 CDT 2015 Marcel Holtmann <marcel@holtmann.org> Bluetooth: Rename bt_cb()->req into bt_cb()->hci
The SKB context buffer for HCI request is really not just for requests, information in their are preserved for the whole HCI layer. So it makes more sense to actually rename it into bt_cb()->hci and also call it then struct hci_ctrl.
In addition that allows moving the decoded opcode for outgoing packets into that struct. So far it was just consuming valuable space from the main shared items. And opcode are not valid for L2CAP packets.
Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
|
H A D | hci_event.c | diff 242c0ebd3730334c43b9c04eeec40d8dd5c3a26e Sun Oct 25 16:45:53 CDT 2015 Marcel Holtmann <marcel@holtmann.org> Bluetooth: Rename bt_cb()->req into bt_cb()->hci
The SKB context buffer for HCI request is really not just for requests, information in their are preserved for the whole HCI layer. So it makes more sense to actually rename it into bt_cb()->hci and also call it then struct hci_ctrl.
In addition that allows moving the decoded opcode for outgoing packets into that struct. So far it was just consuming valuable space from the main shared items. And opcode are not valid for L2CAP packets.
Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
|
H A D | hci_core.c | diff 242c0ebd3730334c43b9c04eeec40d8dd5c3a26e Sun Oct 25 16:45:53 CDT 2015 Marcel Holtmann <marcel@holtmann.org> Bluetooth: Rename bt_cb()->req into bt_cb()->hci
The SKB context buffer for HCI request is really not just for requests, information in their are preserved for the whole HCI layer. So it makes more sense to actually rename it into bt_cb()->hci and also call it then struct hci_ctrl.
In addition that allows moving the decoded opcode for outgoing packets into that struct. So far it was just consuming valuable space from the main shared items. And opcode are not valid for L2CAP packets.
Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
|
/openbmc/linux/include/net/bluetooth/ |
H A D | bluetooth.h | diff 242c0ebd3730334c43b9c04eeec40d8dd5c3a26e Sun Oct 25 16:45:53 CDT 2015 Marcel Holtmann <marcel@holtmann.org> Bluetooth: Rename bt_cb()->req into bt_cb()->hci
The SKB context buffer for HCI request is really not just for requests, information in their are preserved for the whole HCI layer. So it makes more sense to actually rename it into bt_cb()->hci and also call it then struct hci_ctrl.
In addition that allows moving the decoded opcode for outgoing packets into that struct. So far it was just consuming valuable space from the main shared items. And opcode are not valid for L2CAP packets.
Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
|