From: kernel test robot <lkp@intel.com>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-pm@vger.kernel.org
Subject: [amd-pstate:superm1/runtime-pm-screen-on-off 5/5] drivers/platform/x86/asus-wmi.c:4915:25: error: 'asus_hotk_resume_early' undeclared here (not in a function); did you mean 'asus_hotk_resume'?
Date: Sat, 17 Aug 2024 22:21:34 +0800 [thread overview]
Message-ID: <202408172243.JTi2DN1W-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/superm1/linux.git superm1/runtime-pm-screen-on-off
head: 09020cb8f4063731baa98c5f0fd9f1785597c989
commit: 09020cb8f4063731baa98c5f0fd9f1785597c989 [5/5] platform/x86: asus-wmi: Drop CSEE quirks
config: x86_64-buildonly-randconfig-003-20240817 (https://download.01.org/0day-ci/archive/20240817/202408172243.JTi2DN1W-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240817/202408172243.JTi2DN1W-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/202408172243.JTi2DN1W-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/platform/x86/asus-wmi.c:4915:25: error: 'asus_hotk_resume_early' undeclared here (not in a function); did you mean 'asus_hotk_resume'?
4915 | .resume_early = asus_hotk_resume_early,
| ^~~~~~~~~~~~~~~~~~~~~~
| asus_hotk_resume
>> drivers/platform/x86/asus-wmi.c:4916:20: error: 'asus_hotk_prepare' undeclared here (not in a function); did you mean 'asus_hotk_restore'?
4916 | .prepare = asus_hotk_prepare,
| ^~~~~~~~~~~~~~~~~
| asus_hotk_restore
vim +4915 drivers/platform/x86/asus-wmi.c
0773d7f9f1c0ad drivers/platform/x86/eeepc-wmi.c Corentin Chary 2011-02-06 4910
e12e6d94db24e9 drivers/platform/x86/asus-wmi.c Corentin Chary 2011-02-26 4911 static const struct dev_pm_ops asus_pm_ops = {
e12e6d94db24e9 drivers/platform/x86/asus-wmi.c Corentin Chary 2011-02-26 4912 .thaw = asus_hotk_thaw,
e12e6d94db24e9 drivers/platform/x86/asus-wmi.c Corentin Chary 2011-02-26 4913 .restore = asus_hotk_restore,
307340493f3d62 drivers/platform/x86/asus-wmi.c Oleksij Rempel 2015-09-14 4914 .resume = asus_hotk_resume,
e0894ff038d86f drivers/platform/x86/asus-wmi.c Luke D. Jones 2023-11-27 @4915 .resume_early = asus_hotk_resume_early,
e0894ff038d86f drivers/platform/x86/asus-wmi.c Luke D. Jones 2023-11-27 @4916 .prepare = asus_hotk_prepare,
45f2c6937ed606 drivers/platform/x86/eeepc-wmi.c Yong Wang 2010-04-11 4917 };
45f2c6937ed606 drivers/platform/x86/eeepc-wmi.c Yong Wang 2010-04-11 4918
:::::: The code at line 4915 was first introduced by commit
:::::: e0894ff038d86f30614ec16ec26dacb88c8d2bd4 platform/x86: asus-wmi: disable USB0 hub on ROG Ally before suspend
:::::: TO: Luke D. Jones <luke@ljones.dev>
:::::: CC: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-08-17 14:21 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=202408172243.JTi2DN1W-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).