public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [PATCH] tracing: Fix the outmost stupidity of tracing_off()
Date: Fri, 15 Jun 2012 01:12:37 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1206150106511.3086@ionos> (raw)
In-Reply-To: <1339714725.13377.252.camel@gandalf.stny.rr.com>

On Thu, 14 Jun 2012, Steven Rostedt wrote:

> On Fri, 2012-06-15 at 00:47 +0200, Thomas Gleixner wrote:
> > I lost another day of waiting for a complex bug to trigger and turn
> > off tracing, which did not happen due to:
> > 
> >  commit 499e54705(tracing/ring-buffer: Only have tracing_on disable
> >  tracing buffers)
> 
> I submitted this last week: https://lkml.org/lkml/2012/6/6/701

And how does that make up for a lost day?
 
> I forgot to Cc you.

That's still not an excuse for utter stupidity, really. Just check the
commit date vs. your discovery time.

I told you often enough to be more careful, but that one is really
beyond comprehension.

       Thomas

  reply	other threads:[~2012-06-14 23:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14 22:47 [PATCH] tracing: Fix the outmost stupidity of tracing_off() Thomas Gleixner
2012-06-14 22:50 ` Thomas Gleixner
2012-06-14 23:38   ` Steven Rostedt
2012-06-14 22:58 ` Steven Rostedt
2012-06-14 23:12   ` Thomas Gleixner [this message]
2012-06-14 23:48     ` Steven Rostedt
2012-06-15  0:00       ` Thomas Gleixner
2012-06-15  0:32         ` Steven Rostedt
2012-06-15  4:18       ` Steven Rostedt
2012-06-15 11:54         ` Steven Rostedt

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=alpine.LFD.2.02.1206150106511.3086@ionos \
    --to=tglx@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox