lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 9 Apr 2009 06:13:19 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Li Zefan <lizf@...fujitsu.com>,
	Pekka Enberg <penberg@...helsinki.fi>,
	Eduard - Gabriel Munteanu <eduard.munteanu@...ux360.ro>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	Pekka Paalanen <pq@....fi>
Subject: Re: [PATCH][RESEND] tracing: consolidate documents


* Li Zefan <lizf@...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.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ