From: Johan Hedberg <johan.hedberg@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2] Bluetooth: Use bt_dev_err and bt_dev_info when possible
Date: Mon, 30 Oct 2017 14:00:00 +0200 [thread overview]
Message-ID: <20171030120000.GA10743@x1c.lan> (raw)
In-Reply-To: <20171030090441.21322-1-marcel@holtmann.org>
Hi Marcel,
On Mon, Oct 30, 2017, Marcel Holtmann wrote:
> In case of using BT_ERR and BT_INFO, convert to bt_dev_err and
> bt_dev_info when possible. This allows for controller specific
> reporting.
>
> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
> ---
> drivers/bluetooth/bpa10x.c | 15 ++--
> drivers/bluetooth/bt3c_cs.c | 2 +-
> drivers/bluetooth/btbcm.c | 103 ++++++++++++-------------
> drivers/bluetooth/btintel.c | 42 +++++------
> drivers/bluetooth/btqca.c | 6 +-
> drivers/bluetooth/btrtl.c | 21 +++---
> drivers/bluetooth/btusb.c | 155 ++++++++++++++++++--------------------
> drivers/bluetooth/hci_ath.c | 2 +-
> drivers/bluetooth/hci_h4.c | 2 +-
> drivers/bluetooth/hci_qca.c | 12 +--
> drivers/bluetooth/hci_serdev.c | 9 +--
> include/net/bluetooth/bluetooth.h | 3 +
> net/bluetooth/a2mp.c | 2 +-
> net/bluetooth/amp.c | 4 +-
> net/bluetooth/hci_conn.c | 4 +-
> net/bluetooth/hci_core.c | 35 +++++----
> net/bluetooth/hci_event.c | 46 +++++------
> net/bluetooth/hci_request.c | 16 ++--
> net/bluetooth/hci_sysfs.c | 2 +-
> net/bluetooth/mgmt.c | 56 +++++++-------
> net/bluetooth/smp.c | 22 +++---
> 21 files changed, 279 insertions(+), 280 deletions(-)
Applied to bluetooth-next. Thanks.
Johan
prev parent reply other threads:[~2017-10-30 12:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 9:04 [PATCH v2] Bluetooth: Use bt_dev_err and bt_dev_info when possible Marcel Holtmann
2017-10-30 12:00 ` Johan Hedberg [this message]
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=20171030120000.GA10743@x1c.lan \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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;
as well as URLs for NNTP newsgroup(s).