From: kbuild test robot <lkp@intel.com>
To: Kristian Klausen <kristian@klausen.dk>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: drivers/platform/x86/asus-wmi.c:464: undefined reference to `battery_hook_unregister'
Date: Fri, 20 Sep 2019 11:23:43 +0800 [thread overview]
Message-ID: <201909201138.uyiNM7oj%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1761 bytes --]
Hi Kristian,
FYI, the error/warning still remains.
tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 574cc4539762561d96b456dbc0544d8898bd4c6e
commit: 7973353e92ee1e7ca3b2eb361a4b7cb66c92abee platform/x86: asus-wmi: Refactor charge threshold to use the battery hooking API
date: 10 days ago
config: x86_64-randconfig-e001-201937 (attached as .config)
compiler: gcc-7 (Debian 7.4.0-13) 7.4.0
reproduce:
git checkout 7973353e92ee1e7ca3b2eb361a4b7cb66c92abee
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
ld: drivers/platform/x86/asus-wmi.o: in function `asus_wmi_battery_exit':
>> drivers/platform/x86/asus-wmi.c:464: undefined reference to `battery_hook_unregister'
ld: drivers/platform/x86/asus-wmi.o: in function `asus_wmi_battery_init':
>> drivers/platform/x86/asus-wmi.c:457: undefined reference to `battery_hook_register'
vim +464 drivers/platform/x86/asus-wmi.c
451
452 static void asus_wmi_battery_init(struct asus_wmi *asus)
453 {
454 asus->battery_rsoc_available = false;
455 if (asus_wmi_dev_is_present(asus, ASUS_WMI_DEVID_RSOC)) {
456 asus->battery_rsoc_available = true;
> 457 battery_hook_register(&battery_hook);
458 }
459 }
460
461 static void asus_wmi_battery_exit(struct asus_wmi *asus)
462 {
463 if (asus->battery_rsoc_available)
> 464 battery_hook_unregister(&battery_hook);
465 }
466
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 26874 bytes --]
next reply other threads:[~2019-09-20 3:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 3:23 kbuild test robot [this message]
2019-09-20 9:59 ` Andy Shevchenko
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=201909201138.uyiNM7oj%lkp@intel.com \
--to=lkp@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=kbuild-all@01.org \
--cc=kristian@klausen.dk \
--cc=linux-kernel@vger.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 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®