From: kernel test robot <lkp@intel.com>
To: Pan Chuang <panchuang@vivo.com>
Cc: oe-kbuild-all@lists.linux.dev, Ulf Hansson <ulfh@kernel.org>
Subject: [ulfh-pm:next 15/15] drivers/pmdomain/starfive/jh71xx-pmu.c:271:13: warning: variable 'ret' set but not used
Date: Fri, 17 Jul 2026 14:12:54 +0800 [thread overview]
Message-ID: <202607171349.RX0peGoS-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/ulfh/linux-pm.git next
head: ffdca02d427a25b04a6985bcf139ce7602ccc046
commit: ffdca02d427a25b04a6985bcf139ce7602ccc046 [15/15] pmdomain: starfive: Remove redundant dev_err()
config: arc-allyesconfig (https://download.01.org/0day-ci/archive/20260717/202607171349.RX0peGoS-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260717/202607171349.RX0peGoS-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/202607171349.RX0peGoS-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/pmdomain/starfive/jh71xx-pmu.c: In function 'jh7110_pmu_parse_irq':
>> drivers/pmdomain/starfive/jh71xx-pmu.c:271:13: warning: variable 'ret' set but not used [-Wunused-but-set-variable=]
271 | int ret;
| ^~~
vim +/ret +271 drivers/pmdomain/starfive/jh71xx-pmu.c
08b9a94e8654d4 drivers/soc/starfive/jh71xx_pmu.c Walker Chen 2023-01-19 267
296eea56129bdb drivers/pmdomain/starfive/jh71xx-pmu.c Changhuang Liang 2023-09-13 268 static int jh7110_pmu_parse_irq(struct platform_device *pdev, struct jh71xx_pmu *pmu)
296eea56129bdb drivers/pmdomain/starfive/jh71xx-pmu.c Changhuang Liang 2023-09-13 269 {
296eea56129bdb drivers/pmdomain/starfive/jh71xx-pmu.c Changhuang Liang 2023-09-13 270 struct device *dev = &pdev->dev;
296eea56129bdb drivers/pmdomain/starfive/jh71xx-pmu.c Changhuang Liang 2023-09-13 @271 int ret;
296eea56129bdb drivers/pmdomain/starfive/jh71xx-pmu.c Changhuang Liang 2023-09-13 272
296eea56129bdb drivers/pmdomain/starfive/jh71xx-pmu.c Changhuang Liang 2023-09-13 273 pmu->irq = platform_get_irq(pdev, 0);
296eea56129bdb drivers/pmdomain/starfive/jh71xx-pmu.c Changhuang Liang 2023-09-13 274 if (pmu->irq < 0)
296eea56129bdb drivers/pmdomain/starfive/jh71xx-pmu.c Changhuang Liang 2023-09-13 275 return pmu->irq;
296eea56129bdb drivers/pmdomain/starfive/jh71xx-pmu.c Changhuang Liang 2023-09-13 276
296eea56129bdb drivers/pmdomain/starfive/jh71xx-pmu.c Changhuang Liang 2023-09-13 277 ret = devm_request_irq(dev, pmu->irq, jh71xx_pmu_interrupt,
296eea56129bdb drivers/pmdomain/starfive/jh71xx-pmu.c Changhuang Liang 2023-09-13 278 0, pdev->name, pmu);
296eea56129bdb drivers/pmdomain/starfive/jh71xx-pmu.c Changhuang Liang 2023-09-13 279
296eea56129bdb drivers/pmdomain/starfive/jh71xx-pmu.c Changhuang Liang 2023-09-13 280 jh71xx_pmu_int_enable(pmu, JH71XX_PMU_INT_ALL_MASK & ~JH71XX_PMU_INT_PCH_FAIL, true);
296eea56129bdb drivers/pmdomain/starfive/jh71xx-pmu.c Changhuang Liang 2023-09-13 281
296eea56129bdb drivers/pmdomain/starfive/jh71xx-pmu.c Changhuang Liang 2023-09-13 282 return 0;
296eea56129bdb drivers/pmdomain/starfive/jh71xx-pmu.c Changhuang Liang 2023-09-13 283 }
296eea56129bdb drivers/pmdomain/starfive/jh71xx-pmu.c Changhuang Liang 2023-09-13 284
:::::: The code at line 271 was first introduced by commit
:::::: 296eea56129bdb30680d97b5297b2e6c598976f1 pmdomain: starfive: Extract JH7110 pmu private operations
:::::: TO: Changhuang Liang <changhuang.liang@starfivetech.com>
:::::: CC: Ulf Hansson <ulf.hansson@linaro.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-17 6:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202607171349.RX0peGoS-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=panchuang@vivo.com \
--cc=ulfh@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.