From: Arnd Bergmann <arnd@arndb.de>
To: Joe Perches <joe@perches.com>
Cc: Kenneth Heitke <kheitke@codeaurora.org>,
davidb@codeaurora.org, bryanh@codeaurora.org,
linux-arm-msm@vger.kernel.org,
Sagar Dharia <sdharia@codeaurora.org>,
rdunlap@xenotime.net, rmk+kernel@arm.linux.org.uk,
john.stultz@linaro.org, akpm@linux-foundation.org,
ohad@wizery.com, gregkh@suse.de,
Stefan Richter <stefanr@s5r6.in-berlin.de>
Subject: Re: [RFC PATCH] slimbus: Linux driver framework for SLIMbus.
Date: Wed, 24 Aug 2011 16:14:58 +0200 [thread overview]
Message-ID: <201108241614.58800.arnd@arndb.de> (raw)
In-Reply-To: <1314144826.1659.30.camel@Joe-Laptop>
On Wednesday 24 August 2011, Joe Perches wrote:
> It might be reasonable to have slim specific macros/functions
> for message logging. That might allow slim specific prefixes.
>
> For functions, you could look at netdev_<level>:
>
> slim_<level>(struct slim_controller *ctrl, const char *fmt, ...)
>
> or macros like:
>
> #define slim_printk(level, ctrl, fmt, ...) \
> dev_printk(level, &(ctrl)->dev, fmt, ##__VA_ARGS__)
> #define slim_<level>(level, ctrl, fmt, ...) \
> slim_printk(KERN_<LEVEL>, ctrl, fmt, ##__VA_ARGS__)
> etc.
Hi Joe,
My recommendation is always against such macros, and for using the
dev_* and pr_* macros directly. The reason is mostly so that a
causal reader with a kernel background can immediately understand
what they do, rather than having to look up extra macro definition,
e.g. to see if they add the newline character or not.
I agree with all your other comments though, thanks for taking
a look as well.
Arnd
next prev parent reply other threads:[~2011-08-24 14:15 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 23:31 [RFC PATCH] slimbus: Linux driver framework for SLIMbus Kenneth Heitke
2011-08-11 12:55 ` Arnd Bergmann
2011-08-11 20:51 ` Kenneth Heitke
2011-08-12 16:46 ` Mark Brown
2011-08-16 13:37 ` Arnd Bergmann
2011-08-16 13:50 ` David Brown
2011-08-16 14:32 ` Arnd Bergmann
2011-08-16 15:40 ` Mark Brown
2011-08-16 17:13 ` Kenneth Heitke
2011-08-16 17:16 ` Kenneth Heitke
2011-08-16 17:44 ` sdharia
2011-08-16 19:49 ` Arnd Bergmann
2011-08-16 23:27 ` Kenneth Heitke
2011-08-17 0:59 ` Mark Brown
2011-08-17 1:54 ` Sagar Dharia
2011-08-17 6:32 ` Mark Brown
2011-08-17 7:09 ` Arnd Bergmann
2011-08-17 8:03 ` Mark Brown
2011-08-17 10:42 ` Arnd Bergmann
2011-08-17 13:04 ` Mark Brown
2011-08-17 13:17 ` Linus Walleij
2011-08-18 3:00 ` Mark Brown
2011-08-24 9:15 ` Linus Walleij
2011-08-24 9:21 ` Mark Brown
2011-08-25 7:10 ` Linus Walleij
2011-08-25 9:44 ` Mark Brown
2011-08-17 14:00 ` Arnd Bergmann
2011-08-19 3:24 ` Mark Brown
2011-08-21 22:10 ` Sagar Dharia
2011-08-22 13:47 ` Arnd Bergmann
2011-08-16 15:23 ` Mark Brown
2011-08-14 14:34 ` Mark Brown
2011-08-15 17:55 ` Kenneth Heitke
2011-08-15 19:37 ` Russell King
2011-08-15 20:12 ` Kenneth Heitke
2011-08-16 19:33 ` Jean Delvare
2011-08-17 13:12 ` Mark Brown
2011-08-23 23:24 ` Randy Dunlap
2011-08-23 23:32 ` Kenneth Heitke
2011-08-24 0:13 ` Joe Perches
2011-08-24 0:22 ` Kenneth Heitke
2011-08-24 14:14 ` Arnd Bergmann [this message]
2011-08-24 17:24 ` Joe Perches
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=201108241614.58800.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=bryanh@codeaurora.org \
--cc=davidb@codeaurora.org \
--cc=gregkh@suse.de \
--cc=joe@perches.com \
--cc=john.stultz@linaro.org \
--cc=kheitke@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=rdunlap@xenotime.net \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=sdharia@codeaurora.org \
--cc=stefanr@s5r6.in-berlin.de \
/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.