Skip to contentSkip to conversation

tracing: Remove myself as a tracing maintainer

PATCH In review Frederic Weisbecker 3 participants 3 messages May 3, 2014 – May 5, 2014

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 tracing: Remove myself as a tracing maintainer

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 <[email protected]>
Cc Ingo Molnar <[email protected]>
Cc Jiri Olsa <[email protected]>
Cc Masami Hiramatsu <[email protected]>
Cc Namhyung Kim <[email protected]>
Cc Paul E. McKenney <[email protected]>
Cc Peter Zijlstra <[email protected]>
Cc Steven Rostedt <[email protected]>
Cc Thomas Gleixner <[email protected]>
---
 MAINTAINERS | 1 -
 1 file changed, 1 deletion(-)
MAINTAINERS +0 -1
index 6dc67b1..b69be85 100644
@@ -9041,7 +9041,6 @@ F:	drivers/char/tpm/
 
 TRACING
 M:	Steven Rostedt <[email protected]>
-M:	Frederic Weisbecker <[email protected]>
 M:	Ingo Molnar <[email protected]>
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf/core
 S:	Maintained
Signature · 1 line
1.8.3.1
#1 lore raw
Quoted 11 lines · On Sat, 3 May 2014 17:46:31 +0200 Frederic Weisbecker <[email protected]>…

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.

Quoted 5 lines

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

Quoted 27 lines
Cc Arnaldo Carvalho de Melo <[email protected]>
Cc Ingo Molnar <[email protected]>
Cc Jiri Olsa <[email protected]>
Cc Masami Hiramatsu <[email protected]>
Cc Namhyung Kim <[email protected]>
Cc Paul E. McKenney <[email protected]>
Cc Peter Zijlstra <[email protected]>
Cc Steven Rostedt <[email protected]>
Cc Thomas Gleixner <[email protected]>
---
 MAINTAINERS | 1 -
 1 file changed, 1 deletion(-)
MAINTAINERS +0 -1
index 6dc67b1..b69be85 100644
@@ -9041,7 +9041,6 @@ F:	drivers/char/tpm/
 
 TRACING
 M:	Steven Rostedt <[email protected]>
-M:	Frederic Weisbecker <[email protected]>
 M:	Ingo Molnar <[email protected]>
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf/core
 S:	Maintained
#2 lore raw
Quoted 2 lines · Steven Rostedt

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.