From: Yicong Yang <yangyicong@hisilicon.com>
To: kernel test robot <lkp@intel.com>
Cc: <yangyicong@hisilicon.com>, <llvm@lists.linux.dev>,
<kbuild-all@lists.01.org>, <linux-kernel@vger.kernel.org>,
<x86@kernel.org>, Barry Song <baohua@kernel.org>,
Valentin Schneider <valentin.schneider@arm.com>
Subject: Re: [tip:sched/core 45/47] kernel/sched/topology.c:23:20: error: unused function 'sched_debug'
Date: Wed, 13 Oct 2021 17:02:42 +0800 [thread overview]
Message-ID: <0538ccac-19eb-a184-6aef-1d11eefbae17@hisilicon.com> (raw)
In-Reply-To: <202110130209.1XL2cTpW-lkp@intel.com>
Hi,
On 2021/10/13 2:30, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched/core
> head: b2d5b9cec60fecc72a13191c2c6c05acf60975a5
> commit: f43df9225fcad9b07a4ef4d0fe4c3ad2fb4ce82d [45/47] sched/topology: Remove unused numa_distance in cpu_attach_domain()
> config: hexagon-buildonly-randconfig-r004-20211012 (attached as .config)
> compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project c3dcf39554dbea780d6cb7e12239451ba47a2668)
> 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://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=f43df9225fcad9b07a4ef4d0fe4c3ad2fb4ce82d
> git remote add tip https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> git fetch --no-tags tip sched/core
> git checkout f43df9225fcad9b07a4ef4d0fe4c3ad2fb4ce82d
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=hexagon
>
> 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 >>):
>
>>> kernel/sched/topology.c:23:20: error: unused function 'sched_debug' [-Werror,-Wunused-function]
> static inline bool sched_debug(void)
> ^
> 1 error generated.
>
sched_debug() is unused if CONFIG_ENERGY_MODEL=n || CONFIG_CPU_FREQ_GOV_SCHEDUTIL=n and CONFIG_NUMA=n,
which is the case in the report. This is not introduced by this patch.
A __maybe_unused qualify for sched_debug() may fix this. Not sure we intends to do so.
>
> vim +/sched_debug +23 kernel/sched/topology.c
>
> f2cb13609d5397 Ingo Molnar 2017-02-01 22
> f2cb13609d5397 Ingo Molnar 2017-02-01 @23 static inline bool sched_debug(void)
> f2cb13609d5397 Ingo Molnar 2017-02-01 24 {
> 9406415f46f612 Peter Zijlstra 2021-04-15 25 return sched_debug_verbose;
> f2cb13609d5397 Ingo Molnar 2017-02-01 26 }
> f2cb13609d5397 Ingo Molnar 2017-02-01 27
>
> :::::: The code at line 23 was first introduced by commit
> :::::: f2cb13609d5397cdd747f3ed6fb651233851717d sched/topology: Split out scheduler topology code from core.c into topology.c
>
> :::::: TO: Ingo Molnar <mingo@kernel.org>
> :::::: CC: Ingo Molnar <mingo@kernel.org>
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
>
next prev parent reply other threads:[~2021-10-13 9:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 18:30 [tip:sched/core 45/47] kernel/sched/topology.c:23:20: error: unused function 'sched_debug' kernel test robot
2021-10-13 9:02 ` Yicong Yang [this message]
2021-10-13 9:16 ` [kbuild-all] " Philip Li
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=0538ccac-19eb-a184-6aef-1d11eefbae17@hisilicon.com \
--to=yangyicong@hisilicon.com \
--cc=baohua@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=valentin.schneider@arm.com \
--cc=x86@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