From: Marcel Holtmann <marcel@holtmann.org>
To: Joe Perches <joe@perches.com>
Cc: "Gustavo F. Padovan" <padovan@profusion.mobi>,
"David S. Miller" <davem@davemloft.net>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH V2 3/3] bluetooth: Convert BT_DBG to pr_debug
Date: Fri, 17 Feb 2012 09:42:06 +0100 [thread overview]
Message-ID: <1329468126.28848.135.camel@aeonflux> (raw)
In-Reply-To: <6e53178ca0d6ca35c4953e653571d03379759af5.1329461203.git.joe@perches.com>
Hi Joe,
> Add "\n" to uses, align arguments, coalesce formats.
> Fix a typo and fix a bad format extended by a line continuation.
>
> Signed-off-by: Joe Perches <joe@perches.com>
> ---
> drivers/bluetooth/ath3k.c | 10 +-
> drivers/bluetooth/bcm203x.c | 10 +-
> drivers/bluetooth/bfusb.c | 35 +++---
> drivers/bluetooth/bpa10x.c | 30 ++--
> drivers/bluetooth/btmrvl_main.c | 63 +++++-----
> drivers/bluetooth/btmrvl_sdio.c | 27 ++--
> drivers/bluetooth/btsdio.c | 24 ++--
> drivers/bluetooth/btusb.c | 48 ++++----
> drivers/bluetooth/btwilink.c | 17 +--
> drivers/bluetooth/hci_ath.c | 8 +-
> drivers/bluetooth/hci_bcsp.c | 28 ++--
> drivers/bluetooth/hci_h4.c | 10 +-
> drivers/bluetooth/hci_ldisc.c | 23 ++--
> drivers/bluetooth/hci_ll.c | 50 ++++----
> include/net/bluetooth/l2cap.h | 2 +-
> net/bluetooth/af_bluetooth.c | 16 +-
> net/bluetooth/bnep/core.c | 26 ++--
> net/bluetooth/bnep/netdev.c | 12 +-
> net/bluetooth/bnep/sock.c | 6 +-
> net/bluetooth/cmtp/capi.c | 31 +++--
> net/bluetooth/cmtp/core.c | 23 ++--
> net/bluetooth/cmtp/sock.c | 6 +-
> net/bluetooth/hci_conn.c | 58 ++++----
> net/bluetooth/hci_core.c | 151 +++++++++++----------
> net/bluetooth/hci_event.c | 282 ++++++++++++++++++++-------------------
> net/bluetooth/hci_sock.c | 20 ++--
> net/bluetooth/hci_sysfs.c | 8 +-
> net/bluetooth/hidp/core.c | 44 ++++---
> net/bluetooth/hidp/sock.c | 6 +-
> net/bluetooth/l2cap_core.c | 189 ++++++++++++++-------------
> net/bluetooth/l2cap_sock.c | 34 +++---
> net/bluetooth/mgmt.c | 89 ++++++------
> net/bluetooth/rfcomm/core.c | 164 ++++++++++++-----------
> net/bluetooth/rfcomm/sock.c | 49 ++++----
> net/bluetooth/rfcomm/tty.c | 88 ++++++------
> net/bluetooth/sco.c | 69 +++++-----
> net/bluetooth/smp.c | 33 +++---
> 37 files changed, 915 insertions(+), 874 deletions(-)
this one has to wait. You are disturbing multiple developers that are
working on core features.
Regards
Marcel
prev parent reply other threads:[~2012-02-17 8:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 7:32 [PATCH V2 0/3] bluetooth: Shrink object size, use current logging style Joe Perches
2012-02-17 7:32 ` [PATCH V2 1/3] bluetooth: Add logging functions bt_info and bt_err Joe Perches
2012-02-17 8:37 ` Marcel Holtmann
2012-02-17 9:38 ` Johan Hedberg
2012-02-17 7:32 ` [PATCH V2 2/3] bluetooth: Convert BT_ERR/BT_INFO to bt_err/bt_info Joe Perches
2012-02-17 8:40 ` Marcel Holtmann
2012-02-17 9:41 ` Johan Hedberg
2012-02-17 18:12 ` Joe Perches
2012-02-17 7:32 ` [PATCH V2 3/3] bluetooth: Convert BT_DBG to pr_debug Joe Perches
2012-02-17 8:42 ` Marcel Holtmann [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=1329468126.28848.135.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=padovan@profusion.mobi \
/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).