linux-kernel - Re: [PATCH 2/3] ring-buffer: rename debugfs file tracing_on to writing

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]

Message-ID: <alpine.DEB.1.10.0901062145340.25237@gandalf.stny.rr.com>
Date:	Tue, 6 Jan 2009 21:52:01 -0500 (EST)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	linux-kernel@...r.kernel.org, mingo@...e.hu, fweisbec@...il.com,
	roel.kluin@...il.com, pq@....fi, srostedt@...hat.com
Subject: Re: [PATCH 2/3] ring-buffer: rename debugfs file tracing_on to
 writing_enabled

On Tue, 6 Jan 2009, Andrew Morton wrote:

> On Tue, 06 Jan 2009 17:33:39 -0500
> 
> There's no corresponding documentation update needed?

I've fallen a little behind in the documentation. I wanted to see what got 
pulled in before updating ftrace.txt. But you are correct, I probably 
should add the documentation updates along with the patches.

But unfortunately, I'm a bit lazy. I like to wait and see what makes it to 
mainline, and then write a patch to update ftrace.txt to reflect that. It 
lets me do it in one sitting, instead of doing it for each change.

Honestly, I think I document it better that way. If I document right after 
writing the code, I do it with too much knowledge of the code, and my 
writing is confusing for others. If I wait to document, I forget what I 
did, and have to relearn what I wrote, and then I have a better 
perspective of what others will want to know.

Thanks,

-- Steve

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