From: kernel test robot <lkp@intel.com>
To: Qiliang Yuan <realwujing@gmail.com>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>
Cc: oe-kbuild-all@lists.linux.dev,
Qiliang Yuan <realwujing@gmail.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] sched/fair: Cache NUMA node statistics to avoid O(N) scanning
Date: Thu, 29 Jan 2026 19:24:45 +0800 [thread overview]
Message-ID: <202601291924.phVnpnOi-lkp@intel.com> (raw)
In-Reply-To: <20260129031948.2384178-1-realwujing@gmail.com>
Hi Qiliang,
kernel test robot noticed the following build warnings:
[auto build test WARNING on tip/sched/core]
[also build test WARNING on tip/master peterz-queue/sched/core linus/master v6.19-rc7 next-20260128]
[cannot apply to tip/auto-latest]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Qiliang-Yuan/sched-fair-Cache-NUMA-node-statistics-to-avoid-O-N-scanning/20260129-112302
base: tip/sched/core
patch link: https://lore.kernel.org/r/20260129031948.2384178-1-realwujing%40gmail.com
patch subject: [PATCH v4] sched/fair: Cache NUMA node statistics to avoid O(N) scanning
config: arc-allnoconfig (https://download.01.org/0day-ci/archive/20260129/202601291924.phVnpnOi-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260129/202601291924.phVnpnOi-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/202601291924.phVnpnOi-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from kernel/sched/build_utility.c:86:
kernel/sched/topology.c: In function 'init_rootdomain':
>> kernel/sched/topology.c:574:1: warning: label 'free_cpupri' defined but not used [-Wunused-label]
574 | free_cpupri:
| ^~~~~~~~~~~
vim +/free_cpupri +574 kernel/sched/topology.c
571
572 return 0;
573
> 574 free_cpupri:
575 cpupri_cleanup(&rd->cpupri);
576 free_cpudl:
577 cpudl_cleanup(&rd->cpudl);
578 free_rto_mask:
579 free_cpumask_var(rd->rto_mask);
580 free_dlo_mask:
581 free_cpumask_var(rd->dlo_mask);
582 free_online:
583 free_cpumask_var(rd->online);
584 free_span:
585 free_cpumask_var(rd->span);
586 out:
587 return -ENOMEM;
588 }
589
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-01-29 11:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 3:19 Qiliang Yuan
2026-01-29 11:24 ` 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=202601291924.phVnpnOi-lkp@intel.com \
--to=lkp@intel.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=realwujing@gmail.com \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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®