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 v3 00/12] Bluetooth: correct the use of print format
Date: Thu, 3 Jun 2021 15:40:53 +0800 [thread overview]
Message-ID: <1622706065-45409-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.
changes v1 -> v2:
fix some style problems
changes v2 -> v3
fix some commit message style
Kai Ye (12):
Bluetooth: bnep: Use the correct print format
Bluetooth: cmtp: Use the correct print format
Bluetooth: hidp: Use the correct print format
Bluetooth: rfcomm: Use the correct print format
Bluetooth: 6lowpan: Use the correct print format
Bluetooth: a2mp: Use the correct print format
Bluetooth: amp: Use the correct print format
Bluetooth: hci: Use the correct print format
Bluetooth: mgmt: Use the correct print format
Bluetooth: msft: Use the correct print format
Bluetooth: sco: Use the correct print format
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 | 8 +++---
net/bluetooth/cmtp/capi.c | 22 +++++++--------
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 | 68 ++++++++++++++++++++++-----------------------
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, 150 insertions(+), 150 deletions(-)
--
2.8.1
next reply other threads:[~2021-06-03 7:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 7:40 Kai Ye [this message]
2021-06-03 7:40 ` [PATCH v3 01/12] Bluetooth: bnep: Use the correct " Kai Ye
2021-06-03 7:40 ` [PATCH v3 02/12] Bluetooth: cmtp: " Kai Ye
2021-06-03 7:40 ` [PATCH v3 03/12] Bluetooth: hidp: " Kai Ye
2021-06-03 7:40 ` [PATCH v3 04/12] Bluetooth: rfcomm: " Kai Ye
2021-06-03 7:40 ` [PATCH v3 05/12] Bluetooth: 6lowpan: " Kai Ye
2021-06-03 7:40 ` [PATCH v3 06/12] Bluetooth: a2mp: " Kai Ye
2021-06-03 7:41 ` [PATCH v3 07/12] Bluetooth: amp: " Kai Ye
2021-06-03 7:41 ` [PATCH v3 08/12] Bluetooth: hci: " Kai Ye
2021-06-03 7:41 ` [PATCH v3 09/12] Bluetooth: mgmt: " Kai Ye
2021-06-03 7:41 ` [PATCH v3 10/12] Bluetooth: msft: " Kai Ye
2021-06-03 7:41 ` [PATCH v3 11/12] Bluetooth: sco: " Kai Ye
2021-06-03 7:41 ` [PATCH v3 12/12] Bluetooth: smp: " Kai Ye
2021-06-03 14:21 ` [PATCH v3 00/12] Bluetooth: correct the use of " Marcel Holtmann
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=1622706065-45409-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®