Bluetooth: Add clarifying comment for LE CoC result value
The "pending" L2CAP response value is not defined for LE CoC. This patch adds a clarifying comment to the code so that the reader will not think there is a bug in trying to use this value for LE CoC. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
This commit is contained in:
parent
839035a7b3
commit
434714dc02
|
@ -5413,6 +5413,11 @@ static int l2cap_le_connect_req(struct l2cap_conn *conn,
|
||||||
|
|
||||||
if (test_bit(FLAG_DEFER_SETUP, &chan->flags)) {
|
if (test_bit(FLAG_DEFER_SETUP, &chan->flags)) {
|
||||||
l2cap_state_change(chan, BT_CONNECT2);
|
l2cap_state_change(chan, BT_CONNECT2);
|
||||||
|
/* The following result value is actually not defined
|
||||||
|
* for LE CoC but we use it to let the function know
|
||||||
|
* that it should bail out after doing its cleanup
|
||||||
|
* instead of sending a response.
|
||||||
|
*/
|
||||||
result = L2CAP_CR_PEND;
|
result = L2CAP_CR_PEND;
|
||||||
chan->ops->defer(chan);
|
chan->ops->defer(chan);
|
||||||
} else {
|
} else {
|
||||||
|
|
Loading…
Reference in New Issue