From: kernel test robot <lkp@intel.com>
To: "Peter Griffin" <peter.griffin@linaro.org>,
"André Draszik" <andre.draszik@linaro.org>,
"Tudor Ambarus" <tudor.ambarus@linaro.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Alim Akhtar" <alim.akhtar@samsung.com>
Cc: oe-kbuild-all@lists.linux.dev,
William Mcvicker <willmcvicker@google.com>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-team@android.com,
Peter Griffin <peter.griffin@linaro.org>
Subject: Re: [PATCH 2/2] soc: samsung: exynos-pmu: Enable CPU Idle for gs101
Date: Sun, 25 May 2025 16:30:03 +0800 [thread overview]
Message-ID: <202505251653.TsYCp5Mq-lkp@intel.com> (raw)
In-Reply-To: <20250524-gs101-cpuidle-v1-2-aea77a7842a6@linaro.org>
Hi Peter,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 176e917e010cb7dcc605f11d2bc33f304292482b]
url: https://github.com/intel-lab-lkp/linux/commits/Peter-Griffin/arm64-dts-exynos-gs101-Add-local-timer-stop-to-cpuidle-nodes/20250524-153138
base: 176e917e010cb7dcc605f11d2bc33f304292482b
patch link: https://lore.kernel.org/r/20250524-gs101-cpuidle-v1-2-aea77a7842a6%40linaro.org
patch subject: [PATCH 2/2] soc: samsung: exynos-pmu: Enable CPU Idle for gs101
config: arm64-randconfig-r132-20250525 (https://download.01.org/0day-ci/archive/20250525/202505251653.TsYCp5Mq-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce: (https://download.01.org/0day-ci/archive/20250525/202505251653.TsYCp5Mq-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/202505251653.TsYCp5Mq-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/soc/samsung/exynos-pmu.c:593:32: warning: unused variable 'cpupm_pm_ops' [-Wunused-const-variable]
593 | static const struct dev_pm_ops cpupm_pm_ops = {
| ^~~~~~~~~~~~
1 warning generated.
vim +/cpupm_pm_ops +593 drivers/soc/samsung/exynos-pmu.c
592
> 593 static const struct dev_pm_ops cpupm_pm_ops = {
594 .suspend_noirq = exynos_cpupm_suspend_noirq,
595 .resume_noirq = exynos_cpupm_resume_noirq,
596 };
597
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-05-25 8:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-24 7:30 [PATCH 0/2] Enable CPU Idle for gs101 Peter Griffin
2025-05-24 7:30 ` [PATCH 1/2] arm64: dts: exynos: gs101: Add 'local-timer-stop' to cpuidle nodes Peter Griffin
2025-05-24 7:30 ` [PATCH 2/2] soc: samsung: exynos-pmu: Enable CPU Idle for gs101 Peter Griffin
2025-05-25 8:30 ` 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=202505251653.TsYCp5Mq-lkp@intel.com \
--to=lkp@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel-team@android.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peter.griffin@linaro.org \
--cc=robh@kernel.org \
--cc=tudor.ambarus@linaro.org \
--cc=willmcvicker@google.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