From: kernel test robot <lkp@intel.com>
To: Aaron Tomlin <atomlin@atomlin.com>, rafael@kernel.org, dakr@kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
pavel@kernel.org, lenb@kernel.org, neelx@suse.com,
atomlin@atomlin.com, sean@ashe.io, mproche@gmail.com,
chjohnst@gmail.com, nick.lange@gmail.com,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH] PM: QoS: Introduce boot parameter pm_qos_resume_latency_us
Date: Fri, 23 Jan 2026 15:47:39 +0800 [thread overview]
Message-ID: <202601231542.GkFyNtdd-lkp@intel.com> (raw)
In-Reply-To: <20260123010024.3301276-1-atomlin@atomlin.com>
Hi Aaron,
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 rafael-pm/linux-next rafael-pm/bleeding-edge linus/master amd-pstate/linux-next amd-pstate/bleeding-edge v6.19-rc6 next-20260122]
[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/20260123-090409
base: driver-core/driver-core-testing
patch link: https://lore.kernel.org/r/20260123010024.3301276-1-atomlin%40atomlin.com
patch subject: [PATCH] PM: QoS: Introduce boot parameter pm_qos_resume_latency_us
config: s390-allnoconfig (https://download.01.org/0day-ci/archive/20260123/202601231542.GkFyNtdd-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 9b8addffa70cee5b2acc5454712d9cf78ce45710)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260123/202601231542.GkFyNtdd-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/202601231542.GkFyNtdd-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/power/qos.c:56:13: warning: unused variable 'pm_qos_resume_latency_cmdline' [-Wunused-variable]
56 | static char pm_qos_resume_latency_cmdline[COMMAND_LINE_SIZE] __initdata;
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 warning generated.
vim +/pm_qos_resume_latency_cmdline +56 kernel/power/qos.c
55
> 56 static char pm_qos_resume_latency_cmdline[COMMAND_LINE_SIZE] __initdata;
57
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-01-23 7:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 1:00 [PATCH] PM: QoS: Introduce boot parameter pm_qos_resume_latency_us Aaron Tomlin
2026-01-23 6:20 ` kernel test robot
2026-01-23 7:47 ` kernel test robot [this message]
2026-01-23 8:31 ` kernel test robot
2026-01-23 9:25 ` kernel test robot
2026-01-23 9:40 ` kernel test robot
2026-01-23 10:07 ` kernel test robot
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=202601231542.GkFyNtdd-lkp@intel.com \
--to=lkp@intel.com \
--cc=atomlin@atomlin.com \
--cc=chjohnst@gmail.com \
--cc=dakr@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--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=rafael@kernel.org \
--cc=sean@ashe.io \
/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