From: "Theodore Ts'o" <tytso@mit.edu>
To: Linux Kernel Developers List <linux-kernel@vger.kernel.org>
Cc: "Theodore Ts'o" <tytso@mit.edu>, Li Zefan <lizf@cn.fujitsu.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: [PATCH, RFC 1/3] tracing: Update documentation references in kernel/trace/Kconfig
Date: Sat, 11 Apr 2009 15:51:17 -0400 [thread overview]
Message-ID: <1239479479-2603-2-git-send-email-tytso@mit.edu> (raw)
In-Reply-To: <1239479479-2603-1-git-send-email-tytso@mit.edu>
Commit 66bb7488 consolidated documentation files into
Documentation/trace, but it didn't update references found in the
kernel/trace/Kconfig file. Fix this.
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Cc: Li Zefan <lizf@cn.fujitsu.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
---
kernel/trace/Kconfig | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
index 2246141..417d198 100644
--- a/kernel/trace/Kconfig
+++ b/kernel/trace/Kconfig
@@ -312,7 +312,7 @@ config KMEMTRACE
and profile kernel code.
This requires an userspace application to use. See
- Documentation/vm/kmemtrace.txt for more information.
+ Documentation/trace/kmemtrace.txt for more information.
Saying Y will make the kernel somewhat larger and slower. However,
if you disable kmemtrace at run-time or boot-time, the performance
@@ -403,7 +403,7 @@ config MMIOTRACE
implementation and works via page faults. Tracing is disabled by
default and can be enabled at run-time.
- See Documentation/tracers/mmiotrace.txt.
+ See Documentation/trace/mmiotrace.txt.
If you are not helping to develop drivers, say N.
config MMIOTRACE_TEST
--
1.5.6.3
next prev parent reply other threads:[~2009-04-11 20:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-11 19:51 [PATCH, RFC 0/3] Improvements to the tracing documentation Theodore Ts'o
2009-04-11 19:51 ` Theodore Ts'o [this message]
2009-04-11 19:51 ` [PATCH, RFC 2/3] tracing: Document the event tracing system Theodore Ts'o
2009-04-11 19:51 ` [PATCH, RFC 3/3] tracing: Add documentation for the power tracer Theodore Ts'o
2009-04-11 20:44 ` Joe Perches
2009-04-11 21:48 ` Arjan van de Ven
2009-04-12 9:28 ` [tip:tracing/core] " Theodore Ts'o
2009-04-12 13:00 ` Theodore Ts'o
2009-04-12 9:27 ` [tip:tracing/core] tracing: Document the event tracing system Theodore Ts'o
2009-04-12 9:40 ` Cyrill Gorcunov
2009-04-12 13:00 ` Theodore Ts'o
2009-04-12 9:25 ` [PATCH, RFC 0/3] Improvements to the tracing documentation Ingo Molnar
2009-04-12 12:15 ` Theodore Tso
2009-04-12 13:01 ` Ingo Molnar
2009-04-12 17:23 ` Theodore Tso
2009-04-12 17:32 ` [PATCH 1/2] jbd2: Convert instrumentation from markers to tracepoints Theodore Ts'o
2009-04-12 17:32 ` [PATCH 2/2] ext4: " Theodore Ts'o
2009-04-13 21:37 ` Ingo Molnar
2009-04-13 21:31 ` [PATCH, RFC 0/3] Improvements to the tracing documentation Ingo Molnar
2009-04-13 22:35 ` Theodore Tso
2009-04-13 22:55 ` Ingo Molnar
2009-04-13 23:39 ` Theodore Tso
2009-04-13 23:47 ` Ingo Molnar
2009-04-14 5:22 ` Tom Zanussi
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=1239479479-2603-2-git-send-email-tytso@mit.edu \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--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
Powered by JetHome