[PATCH] tracing: Remove myself as a tracing maintainer

[PATCH] tracing: Remove myself as a tracing maintainer

[Frederic Weisbecker]

It has been a while since I last sent a tracing patch. I always keep an
eye on tracing evolutions and contributions in general but given
how busy I am with nohz, isolation and more generally core cleanups stuff,
I seldom have time left to provide deep reviews of tracing patches nor
simply for reviews to begin with.

I've been very lucky to start kernel development on a very young subsystem
with tons of low hanging fruits back in 2008. Given that it deals with
a lot of tricky stuffs all around (sched, timers, irq, preemption, NMIs,
SMP, RCU, ....) I basically learned everything there.

Steve has been doing most of the incredible work these last years.
Thanks a lot!

Of course consider me always available to help on tracing if any hard
days happen.

Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>
Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
---
 MAINTAINERS | 1 -
 1 file changed, 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 6dc67b1..b69be85 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9041,7 +9041,6 @@ 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/tip.git perf/core
 S:	Maintained
-- 
1.8.3.1

Re: [PATCH] tracing: Remove myself as a tracing maintainer

[Steven Rostedt]

On Sat,  3 May 2014 17:46:31 +0200
Frederic Weisbecker <fweisbec@gmail.com> wrote:

> It has been a while since I last sent a tracing patch. I always keep an
> eye on tracing evolutions and contributions in general but given
> how busy I am with nohz, isolation and more generally core cleanups stuff,
> I seldom have time left to provide deep reviews of tracing patches nor
> simply for reviews to begin with.
> 
> I've been very lucky to start kernel development on a very young subsystem
> with tons of low hanging fruits back in 2008. Given that it deals with
> a lot of tricky stuffs all around (sched, timers, irq, preemption, NMIs,
> SMP, RCU, ....) I basically learned everything there.
> 
> Steve has been doing most of the incredible work these last years.
> Thanks a lot!
> 
> Of course consider me always available to help on tracing if any hard
> days happen.

I will reluctantly apply this to my 3.16 queue.

Thanks for all the tracing work! Although, I believe Peter Zijlstra has
some frozen sharks heading your way. ;-)

-- Steve

> 
> Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
> Cc: Ingo Molnar <mingo@kernel.org>
> Cc: Jiri Olsa <jolsa@redhat.com>
> Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
> ---
>  MAINTAINERS | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 6dc67b1..b69be85 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -9041,7 +9041,6 @@ 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/tip.git perf/core
>  S:	Maintained

Re: [PATCH] tracing: Remove myself as a tracing maintainer

[Peter Zijlstra]

On Mon, May 05, 2014 at 11:13:01AM -0400, Steven Rostedt wrote:
> Thanks for all the tracing work! Although, I believe Peter Zijlstra has
> some frozen sharks heading your way. ;-)

Ah yes.. syscall tracing.. the syscall numbers are decimal, the syscall
return value is decimal, but the syscall arguments are hex (without a
0x) prefix.

Confused me properly for a while.