From: Joe Perches <joe@perches.com>
To: David Brown <davidb@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org,
"Daniel Walker" <dwalker@codeaurora.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
"Brian Swetland" <swetland@google.com>,
"Arve Hjønnevåg" <arve@android.com>
Subject: Re: [PATCH v3] msm: smd: Reduce driver log chatter
Date: Wed, 10 Nov 2010 10:24:17 -0800 [thread overview]
Message-ID: <1289413457.15905.95.camel@Joe-Laptop> (raw)
In-Reply-To: <1289411969-24650-1-git-send-email-davidb@codeaurora.org>
On Wed, 2010-11-10 at 09:59 -0800, David Brown wrote:
> arch/arm/mach-msm/smd.c | 18 ++++++++++--------
Hi again David. More trivia. Ignore at your pleasure.
> 1 files changed, 10 insertions(+), 8 deletions(-)
> diff --git a/arch/arm/mach-msm/smd.c b/arch/arm/mach-msm/smd.c
A moderately common kernel style uses macros like:
#define FUNC_ENTER() pr_debug("--> %s\n", __func__);
#define FUNC_EXIT() pr_debug("<-- %s\n", __func__);
or
#define FUNC_ENTER() pr_debug("Enter %s\n", __func__);
#define FUNC_EXIT() pr_debug("Exit %s\n", __func__);
The macro names vary.
I've seen enter, _enter, kenter, func_enter, etc.
> @@ -939,7 +941,7 @@ int smsm_set_sleep_duration(uint32_t delay)
> int smd_core_init(void)
> {
> int r;
> - pr_info("smd_core_init()\n");
> + pr_debug("smd_core_init()\n");
FUNC_ENTER();
> @@ -992,14 +994,14 @@ int smd_core_init(void)
> smsm_change_state(SMSM_STATE_APPS_DEM, ~0, 0);
> #endif
>
> - pr_info("smd_core_init() done\n");
> + pr_debug("smd_core_init() done\n");
FUNC_EXIT();
> static int __devinit msm_smd_probe(struct platform_device *pdev)
> {
> - pr_info("smd_init()\n");
> + pr_debug("smd_init()\n");
wrong function name? FUNC_ENTER();
next prev parent reply other threads:[~2010-11-10 18:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 0:30 [PATCH] msm: smd: Reduce driver log chatter David Brown
2010-11-10 0:49 ` [PATCH v2] " David Brown
2010-11-10 0:56 ` Joe Perches
2010-11-10 17:59 ` [PATCH v3] " David Brown
2010-11-10 18:24 ` Joe Perches [this message]
2010-11-10 18:34 ` Brian Swetland
2010-11-11 22:54 ` [PATCH v4] " David Brown
2010-11-12 4:22 ` Joe Perches
2010-11-12 21:49 ` [PATCH v5] " David Brown
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=1289413457.15905.95.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=arve@android.com \
--cc=davidb@codeaurora.org \
--cc=dwalker@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swetland@google.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