From: Borislav Petkov <bp@alien8.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Juri Lelli <juri.lelli@arm.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Juri Lelli <juri.lelli@gmail.com>
Subject: Re: [PATCH] sched/core: Drop debugging leftover trace_printk call
Date: Fri, 3 Apr 2015 15:28:06 +0200 [thread overview]
Message-ID: <20150403132806.GD3418@pd.tnic> (raw)
In-Reply-To: <20150403092401.2ddbcea8@grimm.local.home>
On Fri, Apr 03, 2015 at 09:24:01AM -0400, Steven Rostedt wrote:
> On Fri, 3 Apr 2015 10:42:50 +0200
> Borislav Petkov <bp@alien8.de> wrote:
>
> > From: Borislav Petkov <bp@suse.de>
> >
> > Commit
> >
> > 3c18d447b3b3 ("sched/core: Check for available DL bandwidth in cpuset_cpu_inactive()")
> >
> > forgot a trace_printk debugging piece in and Steve's banner blew in
> > dmesg. Remove it.
>
> And people say that banner doesn't do anything ;-)
Yeah, that'll teach 'em. And if it weren't that big, I could've just as
well missed it when dmesg whizzes by.
So that banner was a good idea in hindsight!
:-D
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2015-04-03 13:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 8:42 [PATCH] sched/core: Drop debugging leftover trace_printk call Borislav Petkov
2015-04-03 8:51 ` [tip:sched/core] " tip-bot for Borislav Petkov
2015-04-03 13:24 ` [PATCH] " Steven Rostedt
2015-04-03 13:28 ` Borislav Petkov [this message]
2015-04-07 13:47 ` Juri Lelli
2015-04-07 13:56 ` Steven Rostedt
2015-04-07 14:19 ` Juri Lelli
2015-04-07 14:01 ` Joe Perches
2015-04-07 14:10 ` Steven Rostedt
2015-04-07 14:26 ` Joe Perches
2015-04-07 14:34 ` Steven Rostedt
2015-04-07 14:38 ` Peter Zijlstra
2015-04-07 14:43 ` Joe Perches
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=20150403132806.GD3418@pd.tnic \
--to=bp@alien8.de \
--cc=juri.lelli@arm.com \
--cc=juri.lelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
/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.