From: Kai Ye <yekai13@huawei.com>
To: <marcel@holtmann.org>, <johan.hedberg@gmail.com>,
<luiz.dentz@gmail.com>, <davem@davemloft.net>, <kuba@kernel.org>,
<netdev@vger.kernel.org>, <linux-bluetooth@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <yekai13@huawei.com>
Subject: [PATCH 00/12] net/Bluetooth: correct the use of print format
Date: Thu, 20 May 2021 19:44:21 +0800 [thread overview]
Message-ID: <1621511073-47766-1-git-send-email-yekai13@huawei.com> (raw)
According to Documentation/core-api/printk-formats.rst,
Use the correct print format.
1. Printing an unsigned int value should use %u instead of %d.
2. Printing an unsigned long value should use %lu instead of %ld.
Otherwise printk() might end up displaying negative numbers.
Kai Ye (12):
net/Bluetooth/bnep - use the correct print format
net/Bluetooth/cmtp - use the correct print format
net/Bluetooth/hidp - use the correct print format
net/Bluetooth/rfcomm - use the correct print format
net/Bluetooth/6lowpan - use the correct print format
net/Bluetooth/a2mp - use the correct print format
net/Bluetooth/amp - use the correct print format
net/Bluetooth/hci - use the correct print format
net/Bluetooth/mgmt - use the correct print format
net/Bluetooth/msft - use the correct print format
net/Bluetooth/sco - use the correct print format
net/Bluetooth/smp - use the correct print format
net/bluetooth/6lowpan.c | 16 ++++++------
net/bluetooth/a2mp.c | 24 +++++++++---------
net/bluetooth/amp.c | 6 ++---
net/bluetooth/bnep/core.c | 6 ++---
net/bluetooth/cmtp/capi.c | 20 +++++++--------
net/bluetooth/hci_conn.c | 8 +++---
net/bluetooth/hci_core.c | 48 +++++++++++++++++------------------
net/bluetooth/hci_event.c | 24 +++++++++---------
net/bluetooth/hci_request.c | 8 +++---
net/bluetooth/hci_sock.c | 6 ++---
net/bluetooth/hci_sysfs.c | 2 +-
net/bluetooth/hidp/core.c | 6 ++---
net/bluetooth/mgmt.c | 16 ++++++------
net/bluetooth/mgmt_config.c | 4 +--
net/bluetooth/msft.c | 2 +-
net/bluetooth/rfcomm/core.c | 62 ++++++++++++++++++++++-----------------------
net/bluetooth/rfcomm/sock.c | 8 +++---
net/bluetooth/rfcomm/tty.c | 10 ++++----
net/bluetooth/sco.c | 8 +++---
net/bluetooth/smp.c | 6 ++---
20 files changed, 145 insertions(+), 145 deletions(-)
--
2.8.1
next reply other threads:[~2021-05-20 11:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 11:44 Kai Ye [this message]
2021-05-20 11:44 ` [PATCH 01/12] net/Bluetooth/bnep - use the correct print format Kai Ye
2021-05-20 13:32 ` net/Bluetooth: correct the use of " bluez.test.bot
2021-05-20 11:44 ` [PATCH 02/12] net/Bluetooth/cmtp - use the correct " Kai Ye
2021-05-20 11:44 ` [PATCH 03/12] net/Bluetooth/hidp " Kai Ye
2021-05-20 11:44 ` [PATCH 04/12] net/Bluetooth/rfcomm " Kai Ye
2021-05-20 11:44 ` [PATCH 05/12] net/Bluetooth/6lowpan " Kai Ye
2021-05-20 11:44 ` [PATCH 06/12] net/Bluetooth/a2mp " Kai Ye
2021-05-20 11:44 ` [PATCH 07/12] net/Bluetooth/amp " Kai Ye
2021-05-20 11:44 ` [PATCH 08/12] net/Bluetooth/hci " Kai Ye
2021-05-20 11:44 ` [PATCH 09/12] net/Bluetooth/mgmt " Kai Ye
2021-05-20 11:44 ` [PATCH 10/12] net/Bluetooth/msft " Kai Ye
2021-05-20 11:44 ` [PATCH 11/12] net/Bluetooth/sco " Kai Ye
2021-05-20 11:44 ` [PATCH 12/12] net/Bluetooth/smp " Kai Ye
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1621511073-47766-1-git-send-email-yekai13@huawei.com \
--to=yekai13@huawei.com \
--cc=davem@davemloft.net \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.