From: Joe Perches <joe@perches.com>
To: Aloisio Almeida <aloisio.almeida@openbossa.org>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
sameo@linux.intel.com, johannes@sipsolutions.net,
lauro.venancio@openbossa.org, marcio.macedo@openbossa.org,
Waldemar.Rymarkiewicz@tieto.com, padovan@profusion.mobi,
rdunlap@xenotime.net
Subject: Re: [PATCH v4 1/6] NFC: add nfc subsystem core
Date: Tue, 28 Jun 2011 16:52:02 -0700 [thread overview]
Message-ID: <1309305122.29598.43.camel@Joe-Laptop> (raw)
In-Reply-To: <BANLkTikQNMUkS4N7UfCYTAN9TZQzj8pwwQ@mail.gmail.com>
On Tue, 2011-06-28 at 20:31 -0300, Aloisio Almeida wrote:
> Hi Joe,
Oi Aloisio.
> On Tue, Jun 28, 2011 at 5:18 PM, Joe Perches <joe@perches.com> wrote:
> > On Tue, 2011-06-28 at 15:20 -0300, Aloisio Almeida Jr wrote:
> >> From: Lauro Ramos Venancio <lauro.venancio@openbossa.org>
> >> The NFC subsystem core is responsible for providing the device driver
> >> interface. It is also responsible for providing an interface to the control
> >> operations and data exchange.
> > []
> >> diff --git a/net/nfc/nfc.h b/net/nfc/nfc.h
> > []
> >> +#define NFC_INFO(fmt, arg...) printk(KERN_INFO "NFC: " fmt "\n", ## arg)
> >> +#define NFC_ERR(fmt, arg...) printk(KERN_ERR "%s: " fmt "\n", __func__, ## arg)
> >> +#define NFC_DBG(fmt, arg...) pr_debug("%s: " fmt "\n", __func__, ## arg)
> >
> > I think these #defines and their uses would be
> > better lower case.
> >
> > #define nfc_info(etc...)
> > #define nfc_err(etc...)
> > #define nfc_dbg(etc...)
> >
> > And because these don't really take any nfc specific
> > struct as an argument, may be better removed altogether
> > and replaced with the pr_<level> equivalents.
> I was using pr_*() on previous versions. One of the proposed changes
> for v4 was to create these macros to avoid calling pr_*() functions
> with same parameters every time. The implementation chosen is based on
> BT_* macros from bluetooth subsystem.
> > I think emitting __func__ rarely adds useful information.
> I can say that during the implementation phase I considered __func__
> useful, mainly for tracing the execution. That's the reason I left it
> in the code.
Up to you, but regardless, I think the bluetooth macros
aren't good ones to follow. Most all of the other
<foo>_<level> output logging forms are lowercase.
cheers, Joe
next prev parent reply other threads:[~2011-06-28 23:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 18:20 [PATCH v4 0/6] NFC subsystem Aloisio Almeida Jr
2011-06-28 18:20 ` [PATCH v4 1/6] NFC: add nfc subsystem core Aloisio Almeida Jr
2011-06-28 20:18 ` Joe Perches
2011-06-28 23:31 ` Aloisio Almeida
2011-06-28 23:52 ` Joe Perches [this message]
2011-06-29 1:31 ` Marcel Holtmann
2011-06-29 1:49 ` Joe Perches
2011-06-29 18:00 ` Marcel Holtmann
2011-06-29 23:23 ` Aloisio Almeida
2011-06-29 23:46 ` Joe Perches
2011-06-30 3:26 ` Aloisio Almeida
2011-06-30 4:28 ` RFC: Add __dynamic_dev_dbg Joe Perches
2011-06-28 18:20 ` [PATCH v4 2/6] NFC: add nfc generic netlink interface Aloisio Almeida Jr
2011-06-28 18:20 ` [PATCH v4 3/6] NFC: add NFC socket family Aloisio Almeida Jr
2011-06-28 18:20 ` [PATCH v4 4/6] NFC: add the NFC socket raw protocol Aloisio Almeida Jr
2011-06-28 18:20 ` [PATCH v4 5/6] NFC: pn533: add NXP pn533 nfc device driver Aloisio Almeida Jr
2011-06-28 18:20 ` [PATCH v4 6/6] NFC: add Documentation/networking/nfc.txt Aloisio Almeida Jr
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=1309305122.29598.43.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=Waldemar.Rymarkiewicz@tieto.com \
--cc=aloisio.almeida@openbossa.org \
--cc=johannes@sipsolutions.net \
--cc=lauro.venancio@openbossa.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=marcio.macedo@openbossa.org \
--cc=padovan@profusion.mobi \
--cc=rdunlap@xenotime.net \
--cc=sameo@linux.intel.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).