From: kernel test robot <lkp@intel.com>
To: Aaron Tomlin <atomlin@atomlin.com>,
rafael@kernel.org, dakr@kernel.org, pavel@kernel.org,
lenb@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, zhongqiu.han@oss.qualcomm.com,
akpm@linux-foundation.org, bp@alien8.de, pmladek@suse.com,
rdunlap@infradead.org, feng.tang@linux.alibaba.com,
pawan.kumar.gupta@linux.intel.com, kees@kernel.org,
elver@google.com, arnd@arndb.de, fvdl@google.com,
lirongqing@baidu.com, bhelgaas@google.com, neelx@suse.com,
sean@ashe.io, mproche@gmail.com, chjohnst@gmail.com,
nick.lange@gmail.com, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v3] PM: QoS: Introduce boot parameter pm_qos_resume_latency_us
Date: Sun, 8 Mar 2026 05:25:50 +0100 [thread overview]
Message-ID: <202603080526.A162fF4D-lkp@intel.com> (raw)
In-Reply-To: <20260307200736.4192234-1-atomlin@atomlin.com>
Hi Aaron,
kernel test robot noticed the following build errors:
[auto build test ERROR on driver-core/driver-core-testing]
[also build test ERROR on driver-core/driver-core-next driver-core/driver-core-linus rafael-pm/linux-next rafael-pm/bleeding-edge akpm-mm/mm-everything linus/master v6.16-rc1 next-20260306]
[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/Aaron-Tomlin/PM-QoS-Introduce-boot-parameter-pm_qos_resume_latency_us/20260308-040909
base: driver-core/driver-core-testing
patch link: https://lore.kernel.org/r/20260307200736.4192234-1-atomlin%40atomlin.com
patch subject: [PATCH v3] PM: QoS: Introduce boot parameter pm_qos_resume_latency_us
config: i386-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260308/202603080526.A162fF4D-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260308/202603080526.A162fF4D-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/202603080526.A162fF4D-lkp@intel.com/
All errors (new ones prefixed by >>):
>> kernel/power/qos.c:344:5: error: redefinition of 'pm_qos_get_boot_cpu_latency_limit'
344 | s32 pm_qos_get_boot_cpu_latency_limit(unsigned int cpu)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from kernel/power/qos.c:25:
./include/linux/pm_qos.h:222:19: note: previous definition of 'pm_qos_get_boot_cpu_latency_limit' with type 's32(unsigned int)' {aka 'int(unsigned int)'}
222 | static inline s32 pm_qos_get_boot_cpu_latency_limit(unsigned int cpu)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/pm_qos_get_boot_cpu_latency_limit +344 kernel/power/qos.c
332
333 /**
334 * pm_qos_get_boot_cpu_latency_limit - Get boot-time latency limit for a CPU.
335 * @cpu: Logical CPU number to check.
336 *
337 * Checks the read-only boot-time constraints list to see if a specific
338 * PM QoS latency override was requested for this CPU via the kernel
339 * command line.
340 *
341 * Return: The latency limit in microseconds if a constraint exists,
342 * or PM_QOS_RESUME_LATENCY_NO_CONSTRAINT if no boot override applies.
343 */
> 344 s32 pm_qos_get_boot_cpu_latency_limit(unsigned int cpu)
345 {
346 struct pm_qos_boot_entry *entry;
347
348 if (list_empty(&pm_qos_boot_list))
349 return PM_QOS_RESUME_LATENCY_NO_CONSTRAINT;
350
351 list_for_each_entry(entry, &pm_qos_boot_list, node) {
352 if (cpumask_test_cpu(cpu, &entry->mask))
353 return entry->latency;
354 }
355
356 return PM_QOS_RESUME_LATENCY_NO_CONSTRAINT;
357 }
358 EXPORT_SYMBOL_GPL(pm_qos_get_boot_cpu_latency_limit);
359
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-03-08 4:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 20:07 [PATCH v3] PM: QoS: Introduce boot parameter pm_qos_resume_latency_us Aaron Tomlin
2026-03-08 1:02 ` kernel test robot
2026-03-08 4:25 ` 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=202603080526.A162fF4D-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=atomlin@atomlin.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=chjohnst@gmail.com \
--cc=dakr@kernel.org \
--cc=elver@google.com \
--cc=feng.tang@linux.alibaba.com \
--cc=fvdl@google.com \
--cc=kees@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=mproche@gmail.com \
--cc=neelx@suse.com \
--cc=nick.lange@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pavel@kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=pmladek@suse.com \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--cc=sean@ashe.io \
--cc=zhongqiu.han@oss.qualcomm.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