From: kernel test robot <lkp@intel.com>
To: Samuel Kayode <samuel.kayode@savoirfairelinux.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Lee Jones <lee@kernel.org>, Frank Li <Frank.Li@nxp.com>
Subject: drivers/input/misc/pf1550-onkey.c:154:12: warning: 'pf1550_onkey_resume' defined but not used
Date: Sat, 13 Dec 2025 08:45:33 +0800 [thread overview]
Message-ID: <202512130847.kSvqRrBq-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 187d0801404f415f22c0b31531982c7ea97fa341
commit: 9acb215cbebdce721af2219e2859ad17342c9084 Input: pf1550 - add onkey support
date: 7 weeks ago
config: parisc-allyesconfig (https://download.01.org/0day-ci/archive/20251213/202512130847.kSvqRrBq-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251213/202512130847.kSvqRrBq-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/202512130847.kSvqRrBq-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/input/misc/pf1550-onkey.c:154:12: warning: 'pf1550_onkey_resume' defined but not used [-Wunused-function]
154 | static int pf1550_onkey_resume(struct device *dev)
| ^~~~~~~~~~~~~~~~~~~
drivers/input/misc/pf1550-onkey.c:133:12: warning: 'pf1550_onkey_suspend' defined but not used [-Wunused-function]
133 | static int pf1550_onkey_suspend(struct device *dev)
| ^~~~~~~~~~~~~~~~~~~~
vim +/pf1550_onkey_resume +154 drivers/input/misc/pf1550-onkey.c
153
> 154 static int pf1550_onkey_resume(struct device *dev)
155 {
156 struct platform_device *pdev = to_platform_device(dev);
157 struct onkey_drv_data *onkey = platform_get_drvdata(pdev);
158 int i, irq;
159
160 if (!device_may_wakeup(&pdev->dev))
161 regmap_write(onkey->pf1550->regmap,
162 PF1550_PMIC_REG_ONKEY_INT_MASK0,
163 ~((u8)(ONKEY_IRQ_PUSHI | ONKEY_IRQ_1SI |
164 ONKEY_IRQ_2SI | ONKEY_IRQ_3SI | ONKEY_IRQ_4SI |
165 ONKEY_IRQ_8SI)));
166 else
167 for (i = 0; i < PF1550_ONKEY_IRQ_NR; i++) {
168 irq = platform_get_irq(pdev, i);
169 if (irq > 0)
170 disable_irq_wake(irq);
171 }
172
173 return 0;
174 }
175
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-12-13 0:45 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=202512130847.kSvqRrBq-lkp@intel.com \
--to=lkp@intel.com \
--cc=Frank.Li@nxp.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=samuel.kayode@savoirfairelinux.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®