Skip to content
Snippets Groups Projects
Commit 57ddf086 authored by Masahiro Yamada's avatar Masahiro Yamada Committed by Michal Simek
Browse files

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: default avatarMasahiro Yamada <masahiroy@kernel.org>
Link: https://lore.kernel.org/r/20201223152947.698744-1-masahiroy@kernel.org


Signed-off-by: default avatarMichal Simek <michal.simek@xilinx.com>
parent 5c8fe583
No related branches found
No related tags found
No related merge requests found
...@@ -39,7 +39,6 @@ config MICROBLAZE ...@@ -39,7 +39,6 @@ config MICROBLAZE
select OF_EARLY_FLATTREE select OF_EARLY_FLATTREE
select PCI_DOMAINS_GENERIC if PCI select PCI_DOMAINS_GENERIC if PCI
select PCI_SYSCALL if PCI select PCI_SYSCALL if PCI
select TRACING_SUPPORT
select VIRT_TO_BUS select VIRT_TO_BUS
select CPU_NO_EFFICIENT_FFS select CPU_NO_EFFICIENT_FFS
select MMU_GATHER_NO_RANGE select MMU_GATHER_NO_RANGE
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment