From: Masahiro Yamada Date: Wed, 23 Dec 2020 15:29:46 +0000 (+0900) Subject: microblaze: do not select TRACING_SUPPORT directly X-Git-Tag: v5.15~1670^2~2 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=57ddf08642f0b1912c97791413d8c1fe31b6a339;p=platform%2Fkernel%2Flinux-starfive.git microblaze: do not select TRACING_SUPPORT directly Microblaze is the only architecture that selects TRACING_SUPPORT. In my understanding, it is computed by kernel/trace/Kconfig: config TRACING_SUPPORT bool depends on TRACE_IRQFLAGS_SUPPORT depends on STACKTRACE_SUPPORT default y Microblaze enables both TRACE_IRQFLAGS_SUPPORT and STACKTRACE_SUPPORT, so there is no change in the resulted configuration. Signed-off-by: Masahiro Yamada Link: https://lore.kernel.org/r/20201223152947.698744-1-masahiroy@kernel.org Signed-off-by: Michal Simek --- diff --git a/arch/microblaze/Kconfig b/arch/microblaze/Kconfig index f827955..b4ad494 100644 --- a/arch/microblaze/Kconfig +++ b/arch/microblaze/Kconfig @@ -39,7 +39,6 @@ config MICROBLAZE select OF_EARLY_FLATTREE select PCI_DOMAINS_GENERIC if PCI select PCI_SYSCALL if PCI - select TRACING_SUPPORT select VIRT_TO_BUS select CPU_NO_EFFICIENT_FFS select MMU_GATHER_NO_RANGE