mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hui Su <sh_def@163.com>
To: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
	vincent.guittot@linaro.org
Cc: linux-kernel@vger.kernel.org, dietmar.eggemann@arm.com,
	rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
	vschneid@redhat.com, kprateek.nayak@amd.com, elver@google.com,
	jpoimboe@kernel.org, heiko.carstens@de.ibm.com,
	Hui Su <sh_def@163.com>
Subject: [PATCH] sched: Drop the never-defined $(PROFILING) from CFLAGS_core.o
Date: Thu, 22 Oct 2026 15:12:31 +0900	[thread overview]
Message-ID: <20261022061231.610118-1-sh_def@163.com> (raw)

$(PROFILING) is not defined anywhere in the build system, so
"CFLAGS_core.o := $(PROFILING) -fno-omit-frame-pointer" expands to just
"-fno-omit-frame-pointer".  The reference is left over from the days when
the scheduler build rules lived in kernel/Makefile; the ftrace compiler
options moved to CC_FLAGS_FTRACE in c0a80c0c27e5, and KBUILD_CFLAGS adds
those to every object.

Signed-off-by: Hui Su <sh_def@163.com>
---
 kernel/sched/Makefile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/sched/Makefile b/kernel/sched/Makefile
index b1f1a367034f..bd6f4e25e686 100644
--- a/kernel/sched/Makefile
+++ b/kernel/sched/Makefile
@@ -22,7 +22,7 @@ ifneq ($(CONFIG_SCHED_OMIT_FRAME_POINTER),y)
 # me.  I suspect most platforms don't need this, but until we know that for sure
 # I turn this off for IA-64 only.  Andreas Schwab says it's also needed on m68k
 # to get a correct value for the wait-channel (WCHAN in ps). --davidm
-CFLAGS_core.o := $(PROFILING) -fno-omit-frame-pointer
+CFLAGS_core.o := -fno-omit-frame-pointer
 endif
 
 # Branch profiling isn't noinstr-safe


                 reply	other threads:[~2026-10-22  6:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20261022061231.610118-1-sh_def@163.com \
    --to=sh_def@163.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=elver@google.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=jpoimboe@kernel.org \
    --cc=juri.lelli@redhat.com \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®