linux-kernel - Re: [PATCH 0/3] add tracepoints docbook (take #2)

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20090501145528.GA7618@elte.hu>
Date:	Fri, 1 May 2009 16:55:28 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jason Baron <jbaron@...hat.com>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	rostedt@...dmis.org, fweisbec@...il.com,
	mathieu.desnoyers@...ymtl.ca, randy.dunlap@...cle.com,
	wcohen@...hat.com
Subject: Re: [PATCH 0/3] add tracepoints docbook (take #2)


* Jason Baron <jbaron@...hat.com> wrote:

> On Thu, Apr 30, 2009 at 01:29:08PM -0400, Jason Baron wrote:
>
> > The following patches add a new tracepoint docbook. Since 
> > tracepoints can be defined by various macros and in various 
> > files, I think it important to clearly document the available 
> > tracepoints, as Andrew has pointed out. This helps us see what 
> > we have and what we don't have. If this patch is accepted, I 
> > hope that others will add docbook style comments, so we can have 
> > a complete accounting of the kernel's tracepoints.
> > 
> 
> hi,
> 
> i'd also like to get some agreement that future tracepoints need 
> to have this sort of documentation included when they are 
> submitted. Also, I'd like people who have already submitted 
> tracepoints to go back and add this kind of documentation. I'll 
> volunteer to police the effort if we agree it should be done.

sure - but sending patches would be even more useful than policing
:)

	Ingo
--
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/