linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: btusb: Use bt_dev_err for Intel firmware loading errors
Date: Fri, 3 Aug 2018 14:15:51 +0300	[thread overview]
Message-ID: <20180803111551.GA21756@x1c.home> (raw)
In-Reply-To: <20180803092049.14837-1-marcel@holtmann.org>

Hi Marcel,

On Fri, Aug 03, 2018, Marcel Holtmann wrote:
> Replace the BT_ERR functions with bt_dev_err to get a consistent error
> printout that always prefixes the HCI device identifier.
> 
> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
> ---
>  drivers/bluetooth/btusb.c | 77 +++++++++++++++++++--------------------
>  1 file changed, 37 insertions(+), 40 deletions(-)

Applied to bluetooth-next. Thanks.

Johan

      reply	other threads:[~2018-08-03 11:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-03  9:20 [PATCH] Bluetooth: btusb: Use bt_dev_err for Intel firmware loading errors Marcel Holtmann
2018-08-03 11:15 ` 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=20180803111551.GA21756@x1c.home \
    --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).