From: Ingo Molnar <mingo@elte.hu>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Li Zefan <lizf@cn.fujitsu.com>,
Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>,
Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
Pekka Paalanen <pq@iki.fi>
Subject: Re: [PATCH][RESEND] tracing: consolidate documents
Date: Thu, 9 Apr 2009 07:29:12 +0200 [thread overview]
Message-ID: <20090409052912.GG5352@elte.hu> (raw)
In-Reply-To: <84144f020904082216hfb5f5ene87781f9aaf7e76c@mail.gmail.com>
* Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> On Thu, Apr 9, 2009 at 7:13 AM, Ingo Molnar <mingo@elte.hu> wrote:
> >
> > * Li Zefan <lizf@cn.fujitsu.com> wrote:
> >
> >> Li Zefan wrote:
> >> > Move tracepoints.txt, ftrace.txt and mmiotrace.txt to the new
> >> > directory trace/
> >> >
> >>
> >> Should we also move kmemtrace.txt to trace/, or leave it in vm/?
> >
> > Eduard, Pekka, any preferences?
> >
> > Are symbolic links in Documentation/ frowned upon? I think it would
> > be best to have the file in both places:
> >
> > We do want to direct people interested in Documentation/vm/ to
> > kmemtrace ... and we do want to let people who are interested in
> > Documentation/trace/ that there's kmemtrace.
> >
> > Tracing and instrumentation is generally a multi-subsystem thing.
>
> I'm not sure a symbolic link is necessary. Just put it under trace/.
ok - i've amended the commit and have added your Ack - thanks!
Ingo
next prev parent reply other threads:[~2009-04-09 5:29 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 [this message]
2009-04-09 16:37 ` Randy Dunlap
2009-04-09 4:37 ` [tip:tracing/urgent] " Li Zefan
2009-04-09 7:26 ` Mathieu Desnoyers
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=20090409052912.GG5352@elte.hu \
--to=mingo@elte.hu \
--cc=eduard.munteanu@linux360.ro \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mathieu.desnoyers@polymtl.ca \
--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 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.