From: Joe Perches <joe@perches.com>
To: Jingoo Han <jg1.han@samsung.com>
Cc: "'Andrew Morton'" <akpm@linux-foundation.org>,
"'LKML'" <linux-kernel@vger.kernel.org>,
"'Richard Purdie'" <rpurdie@rpsys.net>
Subject: Re: [PATCH v3 3/7] backlight: cr_bllcd: use pr_err/info instead of printk
Date: Wed, 16 May 2012 08:14:24 -0700 [thread overview]
Message-ID: <1337181264.26509.12.camel@joe2Laptop> (raw)
In-Reply-To: <003601cd333b$43094360$c91bca20$%han@samsung.com>
On Wed, 2012-05-16 at 17:09 +0900, Jingoo Han wrote:
> This patch uses pr_err/info instead of printk to allow dynamic debugging.
Hi again.
pr_debug, dev_dbg and netdev_dbg are the only things
that can use dynamic debugging.
All the other levels are just normal logging mechanisms.
prev parent reply other threads:[~2012-05-16 15:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 8:09 [PATCH v3 3/7] backlight: cr_bllcd: use pr_err/info instead of printk Jingoo Han
2012-05-16 15:14 ` Joe Perches [this message]
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=1337181264.26509.12.camel@joe2Laptop \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=jg1.han@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/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