linux-kernel - Re: [RFD tracing] Tracing ABI Work Plan

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 11 Nov 2010 02:55:58 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Steven Rostedt <rostedt@...dmis.org>
cc:	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
	Arnaldo Carvalho de Melo <acme@...radead.org>,
	David Sharp <dhsharp@...gle.com>,
	Arjan van de Ven <arjan@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org
Subject: Re: [RFD tracing] Tracing ABI Work Plan

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!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/