From: kernel test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH ammarfaizi2-block] EXP timers: __pcpu_scope_tick_setup_sched_timer_help_needed can be static
Date: Fri, 7 Jan 2022 15:40:06 +0800 [thread overview]
Message-ID: <20220107074006.GA18912@089a6aeb832b> (raw)
In-Reply-To: <202201071509.qlXBeLQz-lkp@intel.com>
kernel/time/tick-sched.c:1453:1: warning: symbol '__pcpu_scope_tick_setup_sched_timer_help_needed' was not declared. Should it be static?
Fixes: 3cda34a0004e ("EXP timers: Non-nohz_full last-resort jiffies update on IRQ entry")
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
tick-sched.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
index 8790cd4834887c..1af62743be63e8 100644
--- a/kernel/time/tick-sched.c
+++ b/kernel/time/tick-sched.c
@@ -1450,7 +1450,7 @@ early_param("skew_tick", skew_tick);
static DEFINE_PER_CPU(unsigned long, tick_setup_sched_timer_jiffies);
static DEFINE_PER_CPU(int, tick_setup_sched_timer_jiffies_count);
-DEFINE_PER_CPU(bool, tick_setup_sched_timer_help_needed);
+static DEFINE_PER_CPU(bool, tick_setup_sched_timer_help_needed);
/**
* tick_setup_sched_timer - setup the tick emulation timer
prev parent reply other threads:[~2022-01-07 7:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 7:49 [ammarfaizi2-block:paulmck/linux-rcu/dev 50/53] kernel/time/tick-sched.c:1453:1: sparse: sparse: symbol '__pcpu_scope_tick_setup_sched_timer_help_needed' was not declared. Should it be static? kernel test robot
2022-01-07 7:40 ` kernel test robot [this message]
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=20220107074006.GA18912@089a6aeb832b \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome