The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	Arnaldo Carvalho de Melo <acme@infradead.org>,
	David Sharp <dhsharp@google.com>,
	Arjan van de Ven <arjan@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFD tracing] Tracing ABI Work Plan
Date: Thu, 11 Nov 2010 10:10:45 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.00.1011111010160.2900@localhost6.localdomain6> (raw)
In-Reply-To: <1289441127.12418.222.camel@gandalf.stny.rr.com>

On Wed, 10 Nov 2010, Steven Rostedt wrote:
> On Thu, 2010-11-11 at 02:55 +0100, Thomas Gleixner wrote:
> > On Wed, 10 Nov 2010, Steven Rostedt wrote:
> > > On Thu, 2010-11-11 at 02:33 +0100, Thomas Gleixner wrote:
> > > 
> > > > Either that or you immediately install the "Work Plan Committee" which
> > > > will make sure that there will be no progress ever.
> > > 
> > > Oooo ooo oo, I want to be on this committee!!!
> > > 
> > > Get Mathieu and I there, and we can guarantee no work will ever
> > > happen ;-)
> > 
> > Hereby you and Mathieu are appointed to the "Work Plan Committee". By
> > accepting that appointment you promise to stay away from real kernel
> > tracing problems forever and restrict yourself to an annual "no
> > progress" report.
> > 
> > Thanks,
> > 
> > 	tglx
> > ---
> > P.S.: It would be more funny, if it wouldn't be close to reality!
> 
> So be it...

NAK. Just running away is not a technical solution.

> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 0094224..96850d6 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -5889,7 +5889,6 @@ S:	Maintained
>  F:	drivers/char/tpm/
>  
>  TRACING
> -M:	Steven Rostedt <rostedt@goodmis.org>
>  M:	Frederic Weisbecker <fweisbec@gmail.com>
>  M:	Ingo Molnar <mingo@redhat.com>
>  T:	git git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git perf/core
> 
> 

  reply	other threads:[~2010-11-11  9:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-11  0:46 [RFD tracing] Tracing ABI Work Plan Mathieu Desnoyers
2010-11-11  1:33 ` Thomas Gleixner
2010-11-11  1:50   ` Steven Rostedt
2010-11-11  1:55     ` Thomas Gleixner
2010-11-11  2:05       ` Steven Rostedt
2010-11-11  9:10         ` Thomas Gleixner [this message]
2010-11-11  2:16   ` [RFC tracing] Common Trace Format for Linux (v1.1) Mathieu Desnoyers
2010-11-11  9:45     ` Thomas Gleixner
2010-11-11 12:26       ` Mathieu Desnoyers
2010-11-11  7:59 ` [RFD tracing] Tracing ABI Work Plan Masami Hiramatsu
2010-11-11 13:02   ` Mathieu Desnoyers
2010-11-12 11:20     ` Masami Hiramatsu
2010-11-13  1:56     ` David Sharp

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.00.1011111010160.2900@localhost6.localdomain6 \
    --to=tglx@linutronix.de \
    --cc=acme@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=dhsharp@google.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@elte.hu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox