From: Joe Perches <joe@perches.com>
To: Aloisio Almeida <aloisio.almeida@openbossa.org>,
Jason Baron <jbaron@redhat.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
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: Wed, 29 Jun 2011 16:46:03 -0700 [thread overview]
Message-ID: <1309391163.29598.92.camel@Joe-Laptop> (raw)
In-Reply-To: <BANLkTinospg_dhTC8Tcok3kqk9gOryG6eA@mail.gmail.com>
On Wed, 2011-06-29 at 20:23 -0300, Aloisio Almeida wrote:
> >> Today, dynamic_debug can add __func__ to the output as
> >> desired so I think that it's not really necessary
> >> to add to any <foo>_dbg callsite.
> That's true only for pr_debug() function. You cannot add __func__ info
> on dev_dbg() calls dynamically.
I believe that's false. It's definitely stored.
#define dynamic_dev_dbg(dev, fmt, ...) do { \
static struct _ddebug descriptor \
__used \
__attribute__((section("__verbose"), aligned(8))) = \
{ KBUILD_MODNAME, __func__, __FILE__, fmt, __LINE__, \
_DPRINTK_FLAGS_DEFAULT }; \
if (unlikely(descriptor.enabled)) \
dev_printk(KERN_DEBUG, dev, fmt, ##__VA_ARGS__); \
} while (0)
Jason? True or false?
> So, for net/nfc/* I propose to use directly pr_*() functions.
> For device drivers the following macros would be provided:
> #define nfc_dev_info(dev, fmt, arg...) dev_info((dev), "NFC: " fmt, ## arg)
> #define nfc_dev_err(dev, fmt, arg...) dev_err((dev), "%s: " fmt,
> __func__, ## arg)
> #define nfc_dev_dbg(dev, fmt, arg...) dev_dbg((dev), "%s: " fmt,
> __func__, ## arg)
> What do you think?
I still think __func__ isn't useful ;)
I think you should add NFC to nfc_dev_err too.
cheers, Joe
next prev parent reply other threads:[~2011-06-29 23:46 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
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 [this message]
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=1309391163.29598.92.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=Waldemar.Rymarkiewicz@tieto.com \
--cc=aloisio.almeida@openbossa.org \
--cc=jbaron@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=lauro.venancio@openbossa.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=marcel@holtmann.org \
--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