From: kbuild test robot <lkp@intel.com>
To: Ayman Bagabas <ayman.bagabas@gmail.com>
Cc: kbuild-all@01.org, Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
Ayman Bagabas <ayman.bagabas@gmail.com>,
Mattias Jacobsson <2pi@mok.nu>, Takashi Iwai <tiwai@suse.de>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/6] platform/x86: huawei-wmi: Add battery charging thresholds
Date: Thu, 19 Sep 2019 11:08:12 +0800 [thread overview]
Message-ID: <201909191134.IHiA1TYX%lkp@intel.com> (raw)
In-Reply-To: <20190919005505.23822-5-ayman.bagabas@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2523 bytes --]
Hi Ayman,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[cannot apply to v5.3 next-20190918]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Ayman-Bagabas/platform-x86-Huawei-WMI-laptop-extras-driver/20190919-090022
config: x86_64-randconfig-s1-201937 (attached as .config)
compiler: gcc-5 (Ubuntu 5.5.0-12ubuntu1) 5.5.0 20171010
reproduce:
# 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_init':
drivers/platform/x86/asus-wmi.c:457: undefined reference to `battery_hook_register'
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/huawei-wmi.o: in function `huawei_wmi_battery_exit':
>> drivers/platform/x86/huawei-wmi.c:513: undefined reference to `battery_hook_unregister'
ld: drivers/platform/x86/huawei-wmi.o: in function `huawei_wmi_battery_setup':
>> drivers/platform/x86/huawei-wmi.c:504: undefined reference to `battery_hook_register'
vim +513 drivers/platform/x86/huawei-wmi.c
493
494 static void huawei_wmi_battery_setup(struct device *dev)
495 {
496 struct huawei_wmi *huawei = dev_get_drvdata(dev);
497
498 huawei->battery_available = true;
499 if (huawei_wmi_battery_get(NULL, NULL)) {
500 huawei->battery_available = false;
501 return;
502 }
503
> 504 battery_hook_register(&huawei_wmi_battery_hook);
505 device_create_file(dev, &dev_attr_charge_control_thresholds);
506 }
507
508 static void huawei_wmi_battery_exit(struct device *dev)
509 {
510 struct huawei_wmi *huawei = dev_get_drvdata(dev);
511
512 if (huawei->battery_available) {
> 513 battery_hook_unregister(&huawei_wmi_battery_hook);
514 device_remove_file(dev, &dev_attr_charge_control_thresholds);
515 }
516 }
517
---
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: 34230 bytes --]
next prev parent reply other threads:[~2019-09-19 3:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 0:54 [PATCH v2 0/6] platform/x86: Huawei WMI laptop extras driver Ayman Bagabas
2019-09-19 0:54 ` [PATCH v2 1/6] platform/x86: huawei-wmi: Move to platform driver Ayman Bagabas
2019-09-19 0:54 ` [PATCH v2 2/6] platform/x86: huawei-wmi: Add quirks and module parameters Ayman Bagabas
2019-09-19 0:54 ` [PATCH v2 3/6] platform/x86: huawei-wmi: Implement huawei wmi management Ayman Bagabas
2019-09-19 3:22 ` kbuild test robot
2019-09-19 0:54 ` [PATCH v2 4/6] platform/x86: huawei-wmi: Add battery charging thresholds Ayman Bagabas
2019-09-19 3:08 ` kbuild test robot [this message]
2019-09-19 0:54 ` [PATCH v2 5/6] platform/x86: huawei-wmi: Add fn-lock support Ayman Bagabas
2019-09-19 0:54 ` [PATCH v2 6/6] platform/x86: huawei-wmi: Add debugfs support Ayman Bagabas
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=201909191134.IHiA1TYX%lkp@intel.com \
--to=lkp@intel.com \
--cc=2pi@mok.nu \
--cc=andy@infradead.org \
--cc=ayman.bagabas@gmail.com \
--cc=dvhart@infradead.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=tiwai@suse.de \
/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®