All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	stable@kernel.org, greg@kroah.com,
	Chris Wright <chrisw@sous-sol.org>
Subject: Re: [PATCH stable] ftrace document crucial update
Date: Thu, 31 Jul 2008 09:53:44 -0700	[thread overview]
Message-ID: <20080731165335.GA14310@sequoia.sous-sol.org> (raw)
In-Reply-To: <alpine.DEB.1.10.0807302256180.21982@gandalf.stny.rr.com>

* Steven Rostedt (rostedt@goodmis.org) 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.

.txt only patch is quite low-risk, but given the above, is it really that
critical?

thanks,
-chris

      parent reply	other threads:[~2008-07-31 18:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-31  3:05 [PATCH stable] ftrace document crucial update Steven Rostedt
2008-07-31 15:30 ` Jonathan Corbet
2008-07-31 15:50   ` Steven Rostedt
2008-07-31 16:40   ` [PATCH] dual license ftrace.txt Steven Rostedt
2008-07-31 16:48 ` [PATCH stable] ftrace document crucial update Greg KH
2008-07-31 20:10   ` Steven Rostedt
2008-08-01 23:35     ` Greg KH
2008-07-31 16:53 ` Chris Wright [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080731165335.GA14310@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=stable@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.