fix(bt): Fix argument type of ESP_LOGI for spp examples about format error

Closes https://github.com/espressif/esp-idf/pull/11819
This commit is contained in:
chenqingqing 2023-08-04 17:35:59 +08:00
parent a296532715
commit a68c698c67
2 changed files with 2 additions and 2 deletions

View File

@ -107,7 +107,7 @@ static void esp_spp_cb(esp_spp_cb_event_t event, esp_spp_cb_param_t *param)
* rather than in this callback directly. Since the printing takes too much time, it may stuck the Bluetooth * rather than in this callback directly. Since the printing takes too much time, it may stuck the Bluetooth
* stack and also have a effect on the throughput! * stack and also have a effect on the throughput!
*/ */
ESP_LOGI(SPP_TAG, "ESP_SPP_DATA_IND_EVT len:%d handle:%d", ESP_LOGI(SPP_TAG, "ESP_SPP_DATA_IND_EVT len:%d handle:%"PRIu32,
param->data_ind.len, param->data_ind.handle); param->data_ind.len, param->data_ind.handle);
if (param->data_ind.len < 128) { if (param->data_ind.len < 128) {
esp_log_buffer_hex("", param->data_ind.data, param->data_ind.len); esp_log_buffer_hex("", param->data_ind.data, param->data_ind.len);

View File

@ -189,7 +189,7 @@ static void esp_spp_cb(esp_spp_cb_event_t event, esp_spp_cb_param_t *param)
* rather than in this callback directly. Since the printing takes too much time, it may stuck the Bluetooth * rather than in this callback directly. Since the printing takes too much time, it may stuck the Bluetooth
* stack and also have a effect on the throughput! * stack and also have a effect on the throughput!
*/ */
ESP_LOGI(SPP_TAG, "ESP_SPP_WRITE_EVT len:%d handle:%d cong:%d", param->write.len, param->write.handle, ESP_LOGI(SPP_TAG, "ESP_SPP_WRITE_EVT len:%d handle:%"PRIu32" cong:%d", param->write.len, param->write.handle,
param->write.cong); param->write.cong);
if (param->write.len < 128) { if (param->write.len < 128) {
esp_log_buffer_hex("", spp_data, param->write.len); esp_log_buffer_hex("", spp_data, param->write.len);