apache-mynewt-bot removed a comment on pull request #851: URL: https://github.com/apache/mynewt-nimble/pull/851#issuecomment-667121469
<!-- style-bot --> ## Style check summary ### Our coding style is [here!](https://github.com/apache/mynewt-core/blob/master/CODING_STANDARDS.md) #### nimble/host/src/ble_l2cap_coc.c <details> ```diff @@ -209,12 +209,16 @@ struct ble_l2cap_coc_endpoint *rx; uint16_t om_total; int timeout_len = 1000; - // struct ble_l2cap_chan *c; - // struct ble_hs_conn *conn; - - // conn = ble_hs_conn_find_assert(chan->conn_handle); - // c = ble_hs_conn_chan_find_by_scid(conn, chan->scid); - /* Set timeout for receiveing continuation. If timeout + /* + struct ble_l2cap_chan *c; + struct ble_hs_conn *conn; + */ + + /* + conn = ble_hs_conn_find_assert(chan->conn_handle); + c = ble_hs_conn_chan_find_by_scid(conn, chan->scid); + */ + /* Set timeout for receiveing continuation. If timeout * expires, return credits. */ os_callout_stop(&l2cap_continuation_timeout); @@ -248,11 +252,13 @@ BLE_HS_LOG(INFO, "error: sdu_len > rx->mtu (%d>%d)\n", sdu_len, rx->mtu); - // /* Return initial credits */ - // os_callout_stop(&l2cap_continuation_timeout); - // ble_l2cap_sig_le_credits(chan->conn_handle, chan->scid, - // chan->coc_rx.credits); - // /* Disconnect peer with invalid behaviour */ + /* + / * Return initial credits * / + os_callout_stop(&l2cap_continuation_timeout); + ble_l2cap_sig_le_credits(chan->conn_handle, chan->scid, + chan->coc_rx.credits); + / * Disconnect peer with invalid behaviour * / + */ ble_l2cap_disconnect(chan); return BLE_HS_EBADDATA; } @@ -281,7 +287,7 @@ assert(rc == 0); BLE_HS_LOG(DEBUG, "Continuation...received %d\n", (*om)->om_len); - rc = os_mbuf_appendfrom(rx->sdu, *om, 0, om_total); + rc = os_mbuf_appendfrom(rx->sdu, *om, 0, om_total); if (rc != 0) { /* FIXME: need to handle it better */ BLE_HS_LOG(DEBUG, "Could not append data rc=%d\n", rc); ``` </details> ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
