linux-kernel - Re: [PATCH stable] ftrace document crucial update

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] [day] [month] [year] [list]

Message-ID: <20080801233553.GA24276@kroah.com>
Date:	Fri, 1 Aug 2008 16:35:53 -0700
From:	Greg KH <greg@...ah.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	LKML <linux-kernel@...r.kernel.org>, stable@...nel.org,
	Chris Wright <chrisw@...s-sol.org>
Subject: Re: [PATCH stable] ftrace document crucial update

On Thu, Jul 31, 2008 at 04:10:49PM -0400, Steven Rostedt wrote:
> 
> On Thu, 31 Jul 2008, Greg KH wrote:
> 
> > On Wed, Jul 30, 2008 at 11:05:02PM -0400, Steven Rostedt wrote:
> > > 
> > > It has come to my attention that ftrace.txt was pulled into 2.6.26 
> > > prematurely. That is Linus pulled it in before it was well tested. A 
> > > series of updates were made to it shortly afterward, but by then it was 
> > > too late. The release was out, and ftrace.txt was greatly inadequate.
> > > 
> > > This patch is a sum of all the critical updates to keep ftrace.txt in a 
> > > stable state. I strongly urge the stable team to get this into 2.6.26.1.
> > > Otherwise people may be greatly disappointed while reading ftrace.txt just 
> > > to realize that it is horribly out of date.
> > > 
> > > Never mind that ftrace itself doesn't exist is 2.6.26.
> > > 
> > > Signed-off-by: Steven Rostedt <srostedt@...hat.com>
> > 
> > Then why don't I just delete the file from the 2.6.26 tree entirely?
> > That would make more sense, right?
> 
> Nope! I'm leading by example here. We should have good documentation 
> before the code! ;-)

Bah, that only confuses people :)

I'll just go delete the whole thing, makes more sense.  That way you
will not send me patches for the Documentation when things change in the
upstream version...

thanks,

greg k-h
--
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/