From: Jonathan Corbet <corbet@lwn.net>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: changbin.du@intel.com, mingo@kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] Documentation: convert trace/ftrace-design.txt to rst format
Date: Fri, 16 Feb 2018 05:49:52 -0700 [thread overview]
Message-ID: <20180216054952.78718f09@lwn.net> (raw)
In-Reply-To: <20180215225705.58984492@vmware.local.home>
On Thu, 15 Feb 2018 22:57:05 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> This document is out of date, and I rather have it updated before we
> make it more "available" elsewhere.
Imagine that, an out-of-date doc in the kernel :)
Seriously, though, I'd argue that (1) it's already highly available, and
(2) it's useful now. And (3) who knows when that update will happen?
Unless we have reason to believe that a new version is waiting on the
wings, I don't really see why we would want to delay this work.
Thanks,
jon
next prev parent reply other threads:[~2018-02-16 12:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 3:12 [RFC PATCH 0/3] Include linux trace docs to Sphinx TOC tree changbin.du
2018-02-16 3:12 ` [PATCH 1/3] Documentation: add tracing " changbin.du
2018-02-16 3:12 ` [PATCH 2/3] Documentation: convert trace/ftrace-design.txt to rst format changbin.du
2018-02-16 3:57 ` Steven Rostedt
2018-02-16 9:07 ` Du, Changbin
2018-02-16 17:32 ` Steven Rostedt
2018-02-16 12:49 ` Jonathan Corbet [this message]
2018-02-16 17:36 ` Steven Rostedt
2018-02-17 3:30 ` Du, Changbin
2018-02-16 3:12 ` [PATCH 3/3] Documentation: add ftrace-uses.rst to doc tree changbin.du
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=20180216054952.78718f09@lwn.net \
--to=corbet@lwn.net \
--cc=changbin.du@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox