All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masahiro Yamada <masahiroy@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@redhat.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>, linux-kernel@vger.kernel.org
Subject: [PATCH 1/3] ftrace: simplify the Kconfig dependency of FTRACE
Date: Sat, 31 Jul 2021 14:22:31 +0900	[thread overview]
Message-ID: <20210731052233.4703-1-masahiroy@kernel.org> (raw)

The entire FTRACE block is surrounded by 'if TRACING_SUPPORT' ...
'endif'.

Using 'depends on' is a simpler way to guard FTRACE.

Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
---

 kernel/trace/Kconfig | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
index d567b1717c4c..9d3f918b5867 100644
--- a/kernel/trace/Kconfig
+++ b/kernel/trace/Kconfig
@@ -135,10 +135,9 @@ config TRACING_SUPPORT
 	depends on STACKTRACE_SUPPORT
 	default y
 
-if TRACING_SUPPORT
-
 menuconfig FTRACE
 	bool "Tracers"
+	depends on TRACING_SUPPORT
 	default y if DEBUG_KERNEL
 	help
 	  Enable the kernel tracing infrastructure.
@@ -1032,6 +1031,3 @@ config HIST_TRIGGERS_DEBUG
           If unsure, say N.
 
 endif # FTRACE
-
-endif # TRACING_SUPPORT
-
-- 
2.27.0


             reply	other threads:[~2021-07-31  5:23 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-31  5:22 Masahiro Yamada [this message]
2021-07-31  5:22 ` [PATCH 2/3] trace: refactor TRACE_IRQFLAGS_SUPPORT in Kconfig Masahiro Yamada
2021-07-31  5:22   ` Masahiro Yamada
2021-07-31  5:22   ` [OpenRISC] " Masahiro Yamada
2021-07-31  5:22   ` Masahiro Yamada
2021-07-31  5:22   ` Masahiro Yamada
2021-07-31  5:22   ` Masahiro Yamada
2021-07-31  5:22   ` Masahiro Yamada
2021-07-31  6:50   ` Heiko Carstens
2021-07-31  6:50     ` Heiko Carstens
2021-07-31  6:50     ` [OpenRISC] " Heiko Carstens
2021-07-31  6:50     ` Heiko Carstens
2021-07-31  6:50     ` Heiko Carstens
2021-07-31  6:50     ` Heiko Carstens
2021-07-31 23:12   ` Vineet Gupta
2021-07-31 23:12     ` Vineet Gupta
2021-07-31 23:12     ` [OpenRISC] " Vineet Gupta
2021-07-31 23:12     ` Vineet Gupta
2021-07-31 23:12     ` Vineet Gupta
2021-07-31 23:12     ` Vineet Gupta
2021-08-02  2:56   ` Michael Ellerman
2021-08-02  2:56     ` Michael Ellerman
2021-08-02  2:56     ` [OpenRISC] " Michael Ellerman
2021-08-02  2:56     ` Michael Ellerman
2021-08-02  2:56     ` Michael Ellerman
2021-08-02  2:56     ` Michael Ellerman
2021-08-02 15:55   ` Catalin Marinas
2021-08-02 15:55     ` Catalin Marinas
2021-08-02 15:55     ` Catalin Marinas
2021-08-02 15:55     ` Catalin Marinas
2021-08-02 15:55     ` Catalin Marinas
2021-08-02 18:03   ` Max Filippov
2021-08-02 18:03     ` Max Filippov
2021-08-02 18:03     ` [OpenRISC] " Max Filippov
2021-08-02 18:03     ` Max Filippov
2021-08-02 18:03     ` Max Filippov
2021-08-02 18:03     ` Max Filippov
2021-08-25  3:49   ` Palmer Dabbelt
2021-08-25  3:49     ` Palmer Dabbelt
2021-08-25  3:49     ` [OpenRISC] " Palmer Dabbelt
2021-08-25  3:49     ` Palmer Dabbelt
2021-08-25  3:49     ` Palmer Dabbelt
2021-08-25  3:49     ` Palmer Dabbelt
2021-08-25  3:49     ` Palmer Dabbelt
2021-07-31  5:22 ` [PATCH 3/3] trace: remove redundant dependency from IRQSOFF_TRACER Masahiro Yamada
2021-08-02 13:29   ` Steven Rostedt
2021-08-03  5:14     ` Masahiro Yamada

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210731052233.4703-1-masahiroy@kernel.org \
    --to=masahiroy@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.