linux-kernel - [PATCH 0/3] ftrace: separate ftrace from ftrace

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20081006230610.024517480@goodmis.org>
Date:	Mon, 06 Oct 2008 19:06:10 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	linux-kernel@...r.kernel.org
Cc:	Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: [PATCH 0/3] ftrace: separate ftrace from ftrace

There has been a lot of confusion between ftrace the infrastructure and
ftrace the function tracer within ftrace.  Developers have added
dependencies on HAVE_FTRACE when they did not need to. The HAVE_FTRACE
was the architecture supported the function tracer.

This patch series renames the ftrace function tracer to just that,
FUNCTION_TRACER.  And even renames the tracer shown to users from
'ftrace' to 'function'.

Now, when referring to ftrace, it means the ftrace infrastructure, and
when referring to the function trace, it is now called the
function tracer.

The second patch cause a lot of files to be touched. Mostly Makefiles and
Kconfig files. As well as default configs.

-- Steve

--
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/