|author||Mathieu Desnoyers <firstname.lastname@example.org>||2007-10-18 23:41:05 -0700|
|committer||Linus Torvalds <email@example.com>||2007-10-19 11:53:54 -0700|
Combine instrumentation menus in kernel/Kconfig.instrumentation
Quoting Randy: "It seems sad that this patch sources Kconfig.marker, a 7-line file, 20-something times. Yes, you (we) don't want to put those 7 lines into 20-something different files, so sourcing is the right thing. However, what you did for avr32 seems more on the right track to me: make _one_ Instrumentation support menu that includes PROFILING, OPROFILE, KPROBES, and MARKERS and then use (source) that in all of the arches." Signed-off-by: Mathieu Desnoyers <firstname.lastname@example.org> Acked-by: Randy Dunlap <email@example.com> Signed-off-by: Andrew Morton <firstname.lastname@example.org> Signed-off-by: Linus Torvalds <email@example.com>
Diffstat (limited to 'arch/m32r/oprofile')
1 files changed, 0 insertions, 23 deletions
diff --git a/arch/m32r/oprofile/Kconfig b/arch/m32r/oprofile/Kconfig
deleted file mode 100644
@@ -1,23 +0,0 @@
-menu "Profiling support"
- depends on EXPERIMENTAL
- bool "Profiling support (EXPERIMENTAL)"
- Say Y here to enable the extended profiling support mechanisms used
- by profilers such as OProfile.
- tristate "OProfile system profiling (EXPERIMENTAL)"
- depends on PROFILING
- OProfile is a profiling system capable of profiling the
- whole system, include the kernel, kernel modules, libraries,
- and applications.
- If unsure, say N.