From: kernel test robot <lkp@intel.com>
To: Xueqin Luo <luoxueqin@kylinos.cn>,
rafael@kernel.org, viresh.kumar@linaro.org,
sudeep.holla@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, zhanjie9@hisilicon.com,
christian.loehle@arm.com, zhenglifeng1@huawei.com,
sumitg@nvidia.com, lenb@kernel.org,
maciej.wieczor-retman@intel.com, pawel.chmielewski@intel.com,
gregkh@linuxfoundation.org, dakr@kernel.org, johan@kernel.org,
ionela.voinescu@arm.com, pierre.gondois@arm.com,
linux-pm@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, acpica-devel@lists.linux.dev,
driver-core@lists.linux.dev, Xueqin Luo <luoxueqin@kylinos.cn>
Subject: Re: [PATCH v6 3/3] arch_topology: Add topology_update_cpu_capacity() for runtime updates
Date: Wed, 11 Nov 2026 22:14:12 +0800 [thread overview]
Message-ID: <202611112222.Q0bXZAjq-lkp@intel.com> (raw)
In-Reply-To: <20261111085022.1229866-4-luoxueqin@kylinos.cn>
Hi Xueqin,
kernel test robot noticed the following build warnings:
[auto build test WARNING on driver-core/driver-core-testing]
[also build test WARNING on driver-core/driver-core-next driver-core/driver-core-linus amd-pstate/linux-next amd-pstate/bleeding-edge linus/master v7.4-rc2]
[cannot apply to rafael-pm/linux-next rafael-pm/bleeding-edge next-20261110]
[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/Xueqin-Luo/cpufreq-cppc-Add-update_limits-support-for-Highest-Performance-changes/20261111-165020
base: driver-core/driver-core-testing
patch link: https://lore.kernel.org/r/20261111085022.1229866-4-luoxueqin%40kylinos.cn
patch subject: [PATCH v6 3/3] arch_topology: Add topology_update_cpu_capacity() for runtime updates
config: riscv-allnoconfig (https://download.01.org/0day-ci/archive/20261111/202611112222.Q0bXZAjq-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 16.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261111/202611112222.Q0bXZAjq-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/202611112222.Q0bXZAjq-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from include/linux/seqlock.h:20,
from include/linux/mmzone.h:17,
from include/linux/gfp.h:7,
from include/linux/slab.h:17,
from include/linux/resource_ext.h:11,
from include/linux/acpi.h:14,
from drivers/base/arch_topology.c:9:
>> drivers/base/arch_topology.c:232:21: warning: 'raw_capacity_lock' defined but not used [-Wunused-variable]
232 | static DEFINE_MUTEX(raw_capacity_lock);
| ^~~~~~~~~~~~~~~~~
include/linux/mutex.h:87:22: note: in definition of macro 'DEFINE_MUTEX'
87 | struct mutex mutexname = __MUTEX_INITIALIZER(mutexname)
| ^~~~~~~~~
vim +/raw_capacity_lock +232 drivers/base/arch_topology.c
230
231 static u32 *raw_capacity;
> 232 static DEFINE_MUTEX(raw_capacity_lock);
233
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-11-11 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 8:50 [PATCH v6 0/3] cpufreq: cppc: Handle Highest Performance changes at runtime Xueqin Luo
2026-11-11 8:50 ` [PATCH v6 1/3] cpufreq: cppc: Add update_limits support for Highest Performance changes Xueqin Luo
2026-11-11 8:50 ` [PATCH v6 2/3] cpufreq: cppc: Refactor autonomous perf bounds into helper Xueqin Luo
2026-11-11 8:50 ` [PATCH v6 3/3] arch_topology: Add topology_update_cpu_capacity() for runtime updates Xueqin Luo
2026-11-11 14:14 ` 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=202611112222.Q0bXZAjq-lkp@intel.com \
--to=lkp@intel.com \
--cc=acpica-devel@lists.linux.dev \
--cc=christian.loehle@arm.com \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=ionela.voinescu@arm.com \
--cc=johan@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=luoxueqin@kylinos.cn \
--cc=maciej.wieczor-retman@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pawel.chmielewski@intel.com \
--cc=pierre.gondois@arm.com \
--cc=rafael@kernel.org \
--cc=sudeep.holla@kernel.org \
--cc=sumitg@nvidia.com \
--cc=viresh.kumar@linaro.org \
--cc=zhanjie9@hisilicon.com \
--cc=zhenglifeng1@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 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®