From: "Paul E. McKenney" <paulmck@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: [paulmck-rcu:dev.2022.01.04a 55/55] kernel/time/timer.c:1776:6: warning: no previous prototype for 'tick_setup_sched_timer_dump'
Date: Fri, 7 Jan 2022 20:28:49 -0800 [thread overview]
Message-ID: <20220108042849.GS4202@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <202201080834.rGuSv2SS-lkp@intel.com>
On Sat, Jan 08, 2022 at 08:41:32AM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2022.01.04a
> head: 64595d0dff992756e8c6d53c0e9f1e3e50c451f7
> commit: 64595d0dff992756e8c6d53c0e9f1e3e50c451f7 [55/55] squash! EXP timers: Non-nohz_full last-resort jiffies update on IRQ entry
> config: um-i386_defconfig (https://download.01.org/0day-ci/archive/20220108/202201080834.rGuSv2SS-lkp@intel.com/config)
> compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
> reproduce (this is a W=1 build):
> # https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git/commit/?id=64595d0dff992756e8c6d53c0e9f1e3e50c451f7
> git remote add paulmck-rcu https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
> git fetch --no-tags paulmck-rcu dev.2022.01.04a
> git checkout 64595d0dff992756e8c6d53c0e9f1e3e50c451f7
> # save the config file to linux build tree
> mkdir build_dir
> make W=1 O=build_dir ARCH=um SUBARCH=i386 SHELL=/bin/bash kernel/time/
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
Good catch, but this was due to debug code that has since been removed.
Thanx, Paul
> All warnings (new ones prefixed by >>):
>
> kernel/time/timer.c:254:5: warning: no previous prototype for 'timer_migration_handler' [-Wmissing-prototypes]
> 254 | int timer_migration_handler(struct ctl_table *table, int write,
> | ^~~~~~~~~~~~~~~~~~~~~~~
> >> kernel/time/timer.c:1776:6: warning: no previous prototype for 'tick_setup_sched_timer_dump' [-Wmissing-prototypes]
> 1776 | void tick_setup_sched_timer_dump(void)
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
> vim +/tick_setup_sched_timer_dump +1776 kernel/time/timer.c
>
> 1775
> > 1776 void tick_setup_sched_timer_dump(void)
> 1777 {
> 1778 int cpu;
> 1779 int j = jiffies;
> 1780
> 1781 pr_alert("%s state", __func__);
> 1782 for_each_possible_cpu(cpu)
> 1783 pr_cont(" j/c %x/%d %c",
> 1784 (int)(j - per_cpu(tick_setup_sched_timer_jiffies, cpu)) & 0xfff,
> 1785 per_cpu(tick_setup_sched_timer_jiffies_count, cpu),
> 1786 ".H"[per_cpu(tick_setup_sched_timer_help_needed, cpu)]);
> 1787 pr_cont("\n");
> 1788 }
> 1789
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
prev parent reply other threads:[~2022-01-08 4:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 0:41 kernel test robot
2022-01-08 4:28 ` Paul E. McKenney [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=20220108042849.GS4202@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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®