All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Gustavo Padovan <padovan@profusion.mobi>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	"David S. Miller" <davem@davemloft.net>,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] bluetooth: Use more current logging styles
Date: Thu, 16 Feb 2012 08:43:51 -0800	[thread overview]
Message-ID: <1329410631.10890.3.camel@joe2Laptop> (raw)
In-Reply-To: <1329184963.8143.2.camel@joe2Laptop>

On Mon, 2012-02-13 at 18:02 -0800, Joe Perches wrote:
> On Mon, 2012-02-13 at 19:56 -0200, Gustavo Padovan wrote:
> > it is not really a good idea to change BT_INFO to
> > bt_info and BT_ERR to bt_err. I understand that capital letters are not the
> > standard here but such a change is painful for all Bluetooth developers and I
> > don't wanna give more trouble to them.
[]
> Standardization of use and style is a good thing.
> What kind of trouble is a case conversion?
> Out of tree modules?

I'm truly curious as to why you think a
case conversion is painful and trouble.

Backward compatibility could be added via:

#define BT_ERR(fmt, ...)	bt_err(fmt "\n", ##__VA_ARGS__)
#define BT_INFO(fmt, ...)	bt_info(fmt "\n", ##__VA_ARGS__)

  reply	other threads:[~2012-02-16 16:43 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13  3:15 [PATCH 0/2] bluetooth: logging cleanups and trivial object shrinking Joe Perches
2012-02-13  3:15 ` [PATCH 1/2] bluetooth: Use more current logging styles Joe Perches
2012-02-13  6:35   ` Marcel Holtmann
2012-02-13  6:46     ` Joe Perches
2012-02-13  7:21       ` Marcel Holtmann
2012-02-13  7:28         ` Joe Perches
2012-02-13  7:28           ` Joe Perches
2012-02-13  7:30           ` Marcel Holtmann
2012-02-13  7:30             ` Marcel Holtmann
2012-02-13  8:24             ` Joe Perches
2012-02-13  8:24               ` Joe Perches
2012-02-13 21:56     ` Gustavo Padovan
2012-02-13 21:56       ` Gustavo Padovan
2012-02-14  2:02       ` Joe Perches
2012-02-16 16:43         ` Joe Perches [this message]
2012-02-16 18:05           ` Gustavo Padovan
2012-02-16 21:33             ` David Miller
2012-02-17  8:58               ` Marcel Holtmann
2012-02-13  3:15 ` [PATCH 2/2] bluetooth: Convert BT_DBG to pr_debug Joe Perches
2012-02-13  6:37   ` Marcel Holtmann
2012-02-13  6:51     ` Joe Perches
2012-02-13  7:19       ` Marcel Holtmann
2012-02-13  7:24         ` Joe Perches
2012-02-13  7:24           ` Joe Perches
2012-02-13  9:21       ` Andrei Emeltchenko

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=1329410631.10890.3.camel@joe2Laptop \
    --to=joe@perches.com \
    --cc=davem@davemloft.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.