linux-kernel - Re: [PATCH 3/5] tracing/power: move the power trace headers to a dedicated file

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] [day] [month] [year] [list]

Date:	Mon, 9 Feb 2009 10:52:54 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Arjan van de Ven <arjan@...radead.org>
Subject: Re: [PATCH 3/5] tracing/power: move the power trace headers to a
	dedicated file


* Frederic Weisbecker <fweisbec@...il.com> wrote:

> Impact: cleanup
> 
> Move the power tracer headers to trace/power.h to keep ftrace.h and power bits
> more easy to maintain as separated topics.
> 
> Cc: Arjan van de Ven <arjan@...radead.org>
> Cc: Arnaldo Carvalho de Melo <acme@...hat.com>
> Signed-off-by: Frederic Weisbecker <fweisbec@...il.com>
> ---
>  arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c |    2 +-
>  arch/x86/kernel/process.c                  |    2 +-
>  include/linux/ftrace.h                     |   30 ------------------------
>  include/trace/power.h                      |   35 ++++++++++++++++++++++++++++
>  kernel/trace/trace.h                       |    1 +
>  kernel/trace/trace_power.c                 |    2 +-
>  6 files changed, 39 insertions(+), 33 deletions(-)
>  create mode 100644 include/trace/power.h

Applied to tip/tracing/ftrace, thanks Frederic!

	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/