All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Wei Wang <wvw@google.com>
Cc: gregkh@linuxfoundation.org, Wei Wang <wei.vince.wang@gmail.com>,
	Ingo Molnar <mingo@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Kees Cook <keescook@chromium.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>, Crt Mori <cmo@melexis.com>,
	Alexei Starovoitov <ast@kernel.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	linux-kernel@vger.kernel.org, Joe Perches <joe@perches.com>
Subject: Re: [PATCH] do not call trace_printk on non-debug build
Date: Tue, 24 Apr 2018 16:45:05 -0400	[thread overview]
Message-ID: <20180424164505.0a4d15f7@gandalf.local.home> (raw)
In-Reply-To: <CAGXk5yre3aDtVbtEz4=DdBnLrT3U=LPA69jOp9zmkfeYiZ7w=Q@mail.gmail.com>

On Tue, 24 Apr 2018 20:39:27 +0000
Wei Wang <wvw@google.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().

-- Steve

  reply	other threads:[~2018-04-24 20:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24 18:08 [PATCH] do not call trace_printk on non-debug build Wei Wang
2018-04-24 18:50 ` Steven Rostedt
2018-04-24 19:02   ` Wei Wang
2018-04-24 19:14     ` Steven Rostedt
2018-04-24 19:20       ` Wei Wang
2018-04-24 19:26         ` Steven Rostedt
2018-04-24 20:39           ` Wei Wang
2018-04-24 20:45             ` Steven Rostedt [this message]
2018-04-24 20:48               ` Steven Rostedt
2018-04-24 21:32                 ` Wei Wang
2018-04-25  0:49               ` Randy Dunlap
2018-04-25  4:53           ` Wei Wang
2018-04-27  1:46             ` Steven Rostedt
2018-04-25  6:12     ` Greg KH

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=20180424164505.0a4d15f7@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=ast@kernel.org \
    --cc=cmo@melexis.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rdunlap@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=wei.vince.wang@gmail.com \
    --cc=wvw@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 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.