From: Joe Perches <joe@perches.com>
To: Rui Salvaterra <rsalvaterra@gmail.com>,
marcel@holtmann.org, johan.hedberg@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: trivial: tidy up printk message output from btrtl.
Date: Mon, 09 Sep 2019 10:02:25 -0700 [thread overview]
Message-ID: <78acf5cf46bec83c007692be057851a28bed9108.camel@perches.com> (raw)
In-Reply-To: <20190909150329.1779-1-rsalvaterra@gmail.com>
On Mon, 2019-09-09 at 16:03 +0100, Rui Salvaterra wrote:
> The rtl_dev_* calls in the Realtek USB Bluetooth driver add unnecessary
> device prefixes and new lines at the end of most messages, which make the
> dmesg output look like this:
OK, but maybe you could fix this one too:
drivers/bluetooth/hci_h5.c: rtl_dev_err(h5->hu->hdev, "set baud rate command failed\n");
prev parent reply other threads:[~2019-09-09 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 15:03 [PATCH] Bluetooth: trivial: tidy up printk message output from btrtl Rui Salvaterra
2019-09-09 17:02 ` Joe Perches [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=78acf5cf46bec83c007692be057851a28bed9108.camel@perches.com \
--to=joe@perches.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=rsalvaterra@gmail.com \
/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).