linux-kernel - Re: [PATCH, RFC 0/3] Improvements to the tracing documentation

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:	Sun, 12 Apr 2009 15:01:05 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Theodore Tso <tytso@....edu>, Steven Rostedt <rostedt@...dmis.org>,
	Linux Kernel Developers List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH, RFC 0/3] Improvements to the tracing documentation


* Theodore Tso <tytso@....edu> wrote:

> On Sun, Apr 12, 2009 at 11:25:24AM +0200, Ingo Molnar wrote:
> > > I'm not sure the documentation is 100% correct, but by 
> > > submitting it, hopefully that the tracer authors will get 
> > > flushed out of the woodwork and be inspired to improve 
> > > what has been submitted.  :-)
> > 
> > Applied, thanks Ted!
> > 
> > Patch #1 was already present in the tracing tree - i've 
> > added both the event and the power tracer docs to 
> > Documentation/trace/.
> 
> Thanks for applying it so fast, [...]

Heh, i'm used to getting perfect patches from you :) Also, 
documentation is always lagging behind so every little piece helps, 
and it's not like it can actually break anything in the kernel.

> [...] but did you fix up the spelling and pathname 
> (Documentation/power.txt was supposed to be 
> Documentation/trace/power.txt) fixups that folks pointed out?

Yeah, i did that. I also fixed up a few other small details no-one 
pointed out.

> [...] I was going to send an v2 update of the patches.  So if you 
> haven't pushed them out yet, you might want to pull them until I 
> get them fixed up. Or I can send patches to fix up those issues, 
> whichever is more convenient for you.

No need to resend.

Btw., you mention ext4 and jbd2 new-style tracepoints in the text. 
Does this mean you already have them coded up (i havent seen any 
patch posting from you), just that you cannot push it upstream yet 
because ext4 can be a module? We'll have modular new-style 
tracepoints soon.

	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/