The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Dietmar Eggemann <dietmar.eggemann@arm.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	0day robot <lkp@intel.com>
Subject: kernel/sched/sched.h:2664:9: error: implicit declaration of function 'rq_clock_clear_update'; did you mean 'rq_clock_skip_update'?
Date: Thu, 21 Apr 2022 14:45:07 +0800	[thread overview]
Message-ID: <202204211205.jmkEQtvQ-lkp@intel.com> (raw)

tree:   https://github.com/intel-lab-lkp/linux/commits/UPDATE-20220421-031406/Hao-Jia/sched-core-Avoid-obvious-double-update_rq_clock-warning/20220418-171117
head:   9b7d107f881024e9bdcc15a1da7f8a89cd04e14e
commit: 9b7d107f881024e9bdcc15a1da7f8a89cd04e14e sched/core: Avoid obvious double update_rq_clock warning
date:   10 hours ago
config: openrisc-randconfig-r011-20220420 (https://download.01.org/0day-ci/archive/20220421/202204211205.jmkEQtvQ-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/intel-lab-lkp/linux/commit/9b7d107f881024e9bdcc15a1da7f8a89cd04e14e
        git remote add linux-review https://github.com/intel-lab-lkp/linux
        git fetch --no-tags linux-review UPDATE-20220421-031406/Hao-Jia/sched-core-Avoid-obvious-double-update_rq_clock-warning/20220418-171117
        git checkout 9b7d107f881024e9bdcc15a1da7f8a89cd04e14e
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross W=1 O=build_dir ARCH=openrisc SHELL=/bin/bash kernel/

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   In file included from kernel/sched/core.c:81:
   kernel/sched/sched.h: In function 'double_rq_lock':
>> kernel/sched/sched.h:2664:9: error: implicit declaration of function 'rq_clock_clear_update'; did you mean 'rq_clock_skip_update'? [-Werror=implicit-function-declaration]
    2664 |         rq_clock_clear_update(rq1, rq2);
         |         ^~~~~~~~~~~~~~~~~~~~~
         |         rq_clock_skip_update
   kernel/sched/core.c: At top level:
   kernel/sched/core.c:5235:20: warning: no previous prototype for 'task_sched_runtime' [-Wmissing-prototypes]
    5235 | unsigned long long task_sched_runtime(struct task_struct *p)
         |                    ^~~~~~~~~~~~~~~~~~
   kernel/sched/core.c:9432:13: warning: no previous prototype for 'sched_init_smp' [-Wmissing-prototypes]
    9432 | void __init sched_init_smp(void)
         |             ^~~~~~~~~~~~~~
   kernel/sched/core.c:9460:13: warning: no previous prototype for 'sched_init' [-Wmissing-prototypes]
    9460 | void __init sched_init(void)
         |             ^~~~~~~~~~
   cc1: some warnings being treated as errors
--
   In file included from kernel/sched/fair.c:53:
   kernel/sched/sched.h: In function 'double_rq_lock':
>> kernel/sched/sched.h:2664:9: error: implicit declaration of function 'rq_clock_clear_update'; did you mean 'rq_clock_skip_update'? [-Werror=implicit-function-declaration]
    2664 |         rq_clock_clear_update(rq1, rq2);
         |         ^~~~~~~~~~~~~~~~~~~~~
         |         rq_clock_skip_update
   cc1: some warnings being treated as errors
--
   In file included from kernel/sched/build_policy.c:33:
   kernel/sched/sched.h: In function 'double_rq_lock':
>> kernel/sched/sched.h:2664:9: error: implicit declaration of function 'rq_clock_clear_update'; did you mean 'rq_clock_skip_update'? [-Werror=implicit-function-declaration]
    2664 |         rq_clock_clear_update(rq1, rq2);
         |         ^~~~~~~~~~~~~~~~~~~~~
         |         rq_clock_skip_update
   In file included from kernel/sched/build_policy.c:43:
   kernel/sched/rt.c: At top level:
   kernel/sched/rt.c:666:6: warning: no previous prototype for 'sched_rt_bandwidth_account' [-Wmissing-prototypes]
     666 | bool sched_rt_bandwidth_account(struct rt_rq *rt_rq)
         |      ^~~~~~~~~~~~~~~~~~~~~~~~~~
   cc1: some warnings being treated as errors


vim +2664 kernel/sched/sched.h

  2649	
  2650	/*
  2651	 * double_rq_lock - safely lock two runqueues
  2652	 *
  2653	 * Note this does not disable interrupts like task_rq_lock,
  2654	 * you need to do so manually before calling.
  2655	 */
  2656	static inline void double_rq_lock(struct rq *rq1, struct rq *rq2)
  2657		__acquires(rq1->lock)
  2658		__acquires(rq2->lock)
  2659	{
  2660		BUG_ON(!irqs_disabled());
  2661		BUG_ON(rq1 != rq2);
  2662		raw_spin_rq_lock(rq1);
  2663		__acquire(rq2->lock);	/* Fake it out ;) */
> 2664		rq_clock_clear_update(rq1, rq2);
  2665	}
  2666	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-04-21  6:49 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=202204211205.jmkEQtvQ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.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