From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
fweisbec@gmail.com, rostedt@goodmis.org, lizf@cn.fujitsu.com,
pq@iki.fi, tglx@linutronix.de, mingo@elte.hu
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:tracing/urgent] tracing: consolidate documents
Date: Thu, 9 Apr 2009 03:26:38 -0400 [thread overview]
Message-ID: <20090409072638.GA20913@Krystal> (raw)
In-Reply-To: <tip-9f690b04fdf3fa5d7d6abab0bfd8628c3b91d503@git.kernel.org>
* Li Zefan (lizf@cn.fujitsu.com) wrote:
> Commit-ID: 9f690b04fdf3fa5d7d6abab0bfd8628c3b91d503
> Gitweb: http://git.kernel.org/tip/9f690b04fdf3fa5d7d6abab0bfd8628c3b91d503
> Author: Li Zefan <lizf@cn.fujitsu.com>
> AuthorDate: Thu, 9 Apr 2009 11:40:27 +0800
> Committer: Ingo Molnar <mingo@elte.hu>
> CommitDate: Thu, 9 Apr 2009 05:54:42 +0200
>
> tracing: consolidate documents
>
> Move tracepoints.txt, ftrace.txt and mmiotrace.txt to the new
> directory trace/.
>
We should probably move markers.txt while we are at it.
Mathieu
> I didnt find any references to those documents in both source
> files and documents, so no extra work needs to be done.
>
> Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Frederic Weisbecker <fweisbec@gmail.com>
> Cc: Pekka Paalanen <pq@iki.fi>
> Cc: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
> LKML-Reference: <49DD6E2B.6090200@cn.fujitsu.com>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
>
>
> ---
> Documentation/{ => trace}/ftrace.txt | 0
> Documentation/{tracers => trace}/mmiotrace.txt | 0
> Documentation/{ => trace}/tracepoints.txt | 0
> 3 files changed, 0 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/ftrace.txt b/Documentation/trace/ftrace.txt
> similarity index 100%
> rename from Documentation/ftrace.txt
> rename to Documentation/trace/ftrace.txt
> diff --git a/Documentation/tracers/mmiotrace.txt b/Documentation/trace/mmiotrace.txt
> similarity index 100%
> rename from Documentation/tracers/mmiotrace.txt
> rename to Documentation/trace/mmiotrace.txt
> diff --git a/Documentation/tracepoints.txt b/Documentation/trace/tracepoints.txt
> similarity index 100%
> rename from Documentation/tracepoints.txt
> rename to Documentation/trace/tracepoints.txt
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next prev parent reply other threads:[~2009-04-09 7:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 3:40 [PATCH] tracing: consolidate documents Li Zefan
2009-04-09 3:52 ` [PATCH][RESEND] " Li Zefan
2009-04-09 3:59 ` Li Zefan
2009-04-09 4:13 ` Ingo Molnar
2009-04-09 5:16 ` Pekka Enberg
2009-04-09 5:29 ` Ingo Molnar
2009-04-09 16:37 ` Randy Dunlap
2009-04-09 4:37 ` [tip:tracing/urgent] " Li Zefan
2009-04-09 7:26 ` Mathieu Desnoyers [this message]
2009-04-09 5:30 ` Li Zefan
2009-04-09 15:53 ` Pekka Paalanen
2009-04-09 16:58 ` Pekka Enberg
2009-04-10 0:36 ` Li Zefan
2009-04-10 13:04 ` Ingo Molnar
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=20090409072638.GA20913@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=pq@iki.fi \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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