All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org, Pu Lehui <pulehui@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:OLK-6.6 2339/2339] kernel/sched/core.c:158:5: warning: no previous prototype for function 'sched_task_is_throttled'
Date: Fri, 30 May 2025 13:41:43 +0800	[thread overview]
Message-ID: <202505301346.VRD8YS7H-lkp@intel.com> (raw)

tree:   https://gitee.com/openeuler/kernel.git OLK-6.6
head:   f528a77f54d3c07d0b7feb879d2ba15275a4b3ff
commit: b1415ae822e0f2c88266c3f6f8e2b962baa9a579 [2339/2339] interference: Exclude throttle time from rundelay
config: x86_64-buildonly-randconfig-005-20250530 (https://download.01.org/0day-ci/archive/20250530/202505301346.VRD8YS7H-lkp@intel.com/config)
compiler: clang version 20.1.2 (https://github.com/llvm/llvm-project 58df0ef89dd64126512e4ee27b4ac3fd8ddf6247)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250530/202505301346.VRD8YS7H-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202505301346.VRD8YS7H-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> kernel/sched/core.c:158:5: warning: no previous prototype for function 'sched_task_is_throttled' [-Wmissing-prototypes]
     158 | int sched_task_is_throttled(struct task_struct *p, int cpu)
         |     ^
   kernel/sched/core.c:158:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
     158 | int sched_task_is_throttled(struct task_struct *p, int cpu)
         | ^
         | static 
   kernel/sched/core.c:6465:1: warning: unused function 'class_core_lock_lock_ptr' [-Wunused-function]
    6465 | DEFINE_LOCK_GUARD_1(core_lock, int,
         | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    6466 |                     sched_core_lock(*_T->lock, &_T->flags),
         |                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    6467 |                     sched_core_unlock(*_T->lock, &_T->flags),
         |                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    6468 |                     unsigned long flags)
         |                     ~~~~~~~~~~~~~~~~~~~~
   include/linux/cleanup.h:229:49: note: expanded from macro 'DEFINE_LOCK_GUARD_1'
     229 | __DEFINE_CLASS_IS_CONDITIONAL(_name, false);                            \
         |                                                                         ^
     230 | __DEFINE_UNLOCK_GUARD(_name, _type, _unlock, __VA_ARGS__)               \
         | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   include/linux/cleanup.h:205:21: note: expanded from macro '\
   __DEFINE_UNLOCK_GUARD'
     205 | static inline void *class_##_name##_lock_ptr(class_##_name##_t *_T)     \
         |                     ^~~~~~~~~~~~~~~~~~~~~~~~
   <scratch space>:236:1: note: expanded from here
     236 | class_core_lock_lock_ptr
         | ^~~~~~~~~~~~~~~~~~~~~~~~
   2 warnings generated.


vim +/sched_task_is_throttled +158 kernel/sched/core.c

   156	
   157	#if defined(CONFIG_SCHED_CORE) || defined(CONFIG_CGROUP_IFS)
 > 158	int sched_task_is_throttled(struct task_struct *p, int cpu)
   159	{
   160		if (p->sched_class->task_is_throttled)
   161			return p->sched_class->task_is_throttled(p, cpu);
   162	
   163		return 0;
   164	}
   165	#endif
   166	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2025-05-30  5:42 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=202505301346.VRD8YS7H-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kernel@openeuler.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pulehui@huawei.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 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.