[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e9195edc-8661-f4d7-eb0b-ac839eea1974@infradead.org>
Date: Tue, 24 Apr 2018 17:49:06 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Steven Rostedt <rostedt@...dmis.org>, Wei Wang <wvw@...gle.com>
Cc: gregkh@...uxfoundation.org, Wei Wang <wei.vince.wang@...il.com>,
Ingo Molnar <mingo@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Kees Cook <keescook@...omium.org>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Crt Mori <cmo@...exis.com>,
Alexei Starovoitov <ast@...nel.org>,
linux-kernel@...r.kernel.org, Joe Perches <joe@...ches.com>
Subject: Re: [PATCH] do not call trace_printk on non-debug build
On 04/24/2018 01:45 PM, Steven Rostedt wrote:
> On Tue, 24 Apr 2018 20:39:27 +0000
> Wei Wang <wvw@...gle.com> wrote:
>
>> The config is not something new and it is controlling pr_debug and
>> pr_devel, so might not be too annoying, IMHO. But I agree this is not a
>> problem from us but from abusers.
>
> And is the reason I never use pr_debug() and pr_devel().
pr_debug() is good along with dynamic debug.
--
~Randy
Powered by blists - more mailing lists