lkml.org 
[lkml]   [2021]   [Jun]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH v3 10/12] Bluetooth: msft: Use the correct print format
    Date
    According to Documentation/core-api/printk-formats.rst,
    Use the correct print format. Printing an unsigned int value should use %u
    instead of %d. Otherwise printk() might end up displaying negative numbers.

    Signed-off-by: Kai Ye <yekai13@huawei.com>
    ---
    net/bluetooth/msft.c | 2 +-
    1 file changed, 1 insertion(+), 1 deletion(-)

    diff --git a/net/bluetooth/msft.c b/net/bluetooth/msft.c
    index 47b104f..8d2310e 100644
    --- a/net/bluetooth/msft.c
    +++ b/net/bluetooth/msft.c
    @@ -308,7 +308,7 @@ static void msft_le_monitor_advertisement_cb(struct hci_dev *hdev,

    monitor = idr_find(&hdev->adv_monitors_idr, msft->pending_add_handle);
    if (!monitor) {
    - bt_dev_err(hdev, "msft add advmon: monitor %d is not found!",
    + bt_dev_err(hdev, "msft add advmon: monitor %u is not found!",
    msft->pending_add_handle);
    status = HCI_ERROR_UNSPECIFIED;
    goto unlock;
    --
    2.8.1
    \
     
     \ /
      Last update: 2021-06-03 09:45    [W:2.970 / U:0.092 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site