public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Pekka Enberg <penberg@cs.helsinki.fi>, Pekka Paalanen <pq@iki.fi>,
	eduard.munteanu@linux360.ro, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tracing: fix document references
Date: Fri, 10 Apr 2009 08:50:55 +0800	[thread overview]
Message-ID: <49DE97EF.7080208@cn.fujitsu.com> (raw)
In-Reply-To: <49DE9764.1090004@cn.fujitsu.com>

CC: LKML

Li Zefan wrote:
> When moving documents to Documentation/trace/, I forgot to
> grep Kconfig to find out those references.
> 
> Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
> ---
>  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


       reply	other threads:[~2009-04-10  0:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49DE9764.1090004@cn.fujitsu.com>
2009-04-10  0:50 ` Li Zefan [this message]
2009-04-10 11:12   ` [tip:tracing/urgent] tracing: fix document references Li Zefan

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=49DE97EF.7080208@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=eduard.munteanu@linux360.ro \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=penberg@cs.helsinki.fi \
    --cc=pq@iki.fi \
    --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