From: Larry Finger <Larry.Finger@lwfinger.net>
To: Borislav Petkov <bp@alien8.de>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Joe Perches <joe@perches.com>
Subject: Re: CONFIG_RTLWIFI_DEBUG default y
Date: Mon, 02 Apr 2012 12:45:09 -0500 [thread overview]
Message-ID: <4F79E5A5.9000004@lwfinger.net> (raw)
In-Reply-To: <20120402171733.GB13264@x1.osrc.amd.com>
On 04/02/2012 12:17 PM, Borislav Petkov wrote:
> On Mon, Apr 02, 2012 at 09:53:38AM -0700, Joe Perches wrote:
>> To keep all the "printk(KERN_DEBUG" to "pr_debug(" conversion
>> output the same as the it was prior to the patch.
>>
>> Larry can default it to off if he wants.
>
>> From looking at one user of this -
> drivers/net/wireless/rtlwifi/rtl8192ce/hw.c - some of the messages look
> like important ones which you wanna have enabled always, f.e. error
> handling in rtl92ce_hw_init().
>
> It probably needs splitting into debugging messages which are default n
> and always-on messages.
The current situation is fine with me. Any user with an embedded system can save
a lot of memory by setting CONFIG_RTLWIFI_DEBUG to n. If a normal distro chooses
to do that, then when some user of that distro reports a problem and is unable
to run with the module parameter "debug=X", I get to say "Sorry, I cannot help
you." :)
Of course, if you want to go through the source and convert every instance of
"RT_TRACE(rtlpriv, COMP_ERR, DBG_EMERG, ...)" to the equivalent "pr_err(...),
then I would probably sign off on it.
Larry
next prev parent reply other threads:[~2012-04-02 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 16:49 CONFIG_RTLWIFI_DEBUG default y Borislav Petkov
2012-04-02 16:53 ` Joe Perches
2012-04-02 17:17 ` Borislav Petkov
2012-04-02 17:29 ` Joe Perches
2012-04-02 17:45 ` Larry Finger [this message]
2012-04-02 18:08 ` Joe Perches
2012-04-02 20:32 ` Borislav Petkov
2012-04-02 20:46 ` Larry Finger
2012-04-02 20:53 ` Borislav Petkov
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=4F79E5A5.9000004@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bp@alien8.de \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 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.