From: kbuild test robot <lkp@intel.com>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>
Cc: kbuild-all@01.org, linux-leds@vger.kernel.org
Subject: [j.anaszewski-leds:for-next 56/57] include/linux/leds.h:191: undefined reference to `devm_led_classdev_register_ext'
Date: Wed, 28 Aug 2019 17:14:09 +0800 [thread overview]
Message-ID: <201908281748.ym4r5V40%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1756 bytes --]
tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/j.anaszewski/linux-leds.git for-next
head: 5add28d2f3575dffa33a9122e47c13c2374b5b31
commit: ea4117e6feaa0b5060a2529fe240626e55420adf [56/57] leds: Replace {devm_}led_classdev_register() macros with inlines
config: i386-randconfig-h002-201934 (attached as .config)
compiler: gcc-7 (Debian 7.4.0-10) 7.4.0
reproduce:
git checkout ea4117e6feaa0b5060a2529fe240626e55420adf
# save the attached .config to linux build tree
make ARCH=i386
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/input/keyboard/applespi.o: in function `devm_led_classdev_register':
>> include/linux/leds.h:191: undefined reference to `devm_led_classdev_register_ext'
vim +191 include/linux/leds.h
183
184 extern int devm_led_classdev_register_ext(struct device *parent,
185 struct led_classdev *led_cdev,
186 struct led_init_data *init_data);
187
188 static inline int devm_led_classdev_register(struct device *parent,
189 struct led_classdev *led_cdev)
190 {
> 191 return devm_led_classdev_register_ext(parent, led_cdev, NULL);
192 }
193 extern void led_classdev_unregister(struct led_classdev *led_cdev);
194 extern void devm_led_classdev_unregister(struct device *parent,
195 struct led_classdev *led_cdev);
196 extern void led_classdev_suspend(struct led_classdev *led_cdev);
197 extern void led_classdev_resume(struct led_classdev *led_cdev);
198
---
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: 28807 bytes --]
reply other threads:[~2019-08-28 9:15 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=201908281748.ym4r5V40%lkp@intel.com \
--to=lkp@intel.com \
--cc=jacek.anaszewski@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-leds@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;
as well as URLs for NNTP newsgroup(s).