diff options
| author | Masahiro Yamada <[email protected]> | 2020-12-24 00:29:46 +0900 |
|---|---|---|
| committer | Michal Simek <[email protected]> | 2021-01-04 10:42:04 +0100 |
| commit | 57ddf08642f0b1912c97791413d8c1fe31b6a339 (patch) | |
| tree | 0e1613269f9a23219434b978140633ba0c0bef5c | |
| parent | 5c8fe583cce542aa0b84adc939ce85293de36e5e (diff) | |
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 <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Michal Simek <[email protected]>
| -rw-r--r-- | arch/microblaze/Kconfig | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/arch/microblaze/Kconfig b/arch/microblaze/Kconfig index f82795592ce5..b4ad4943d078 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 |