From: kbuild test robot <lkp@intel.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: drivers/gpu/drm/bridge/sil-sii8620.c:2405: undefined reference to `extcon_unregister_notifier'
Date: Sat, 5 May 2018 01:57:57 +0800 [thread overview]
Message-ID: <201805050142.teMqO83j%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2906 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 625e2001e99e82ea3eb5b0370a428a4328b9166b
commit: eb27fde2731b6cb5818493b8ac18e01f427e335f eeprom: at24: drop redundant variable in at24_read()
date: 6 weeks ago
config: x86_64-randconfig-g0-05042232 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
git checkout eb27fde2731b6cb5818493b8ac18e01f427e335f
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/gpu/drm/bridge/sil-sii8620.o: In function `sii8620_remove':
>> /kbuild/src/smoke/drivers/gpu/drm/bridge/sil-sii8620.c:2405: undefined reference to `extcon_unregister_notifier'
drivers/gpu/drm/bridge/sil-sii8620.o: In function `sii8620_extcon_work':
>> /kbuild/src/smoke/drivers/gpu/drm/bridge/sil-sii8620.c:2189: undefined reference to `extcon_get_state'
--
drivers/gpu/drm/bridge/sil-sii8620.o: In function `sii8620_remove':
>> drivers/gpu/drm/bridge/sil-sii8620.c:2405: undefined reference to `extcon_unregister_notifier'
drivers/gpu/drm/bridge/sil-sii8620.o: In function `sii8620_extcon_work':
>> drivers/gpu/drm/bridge/sil-sii8620.c:2189: undefined reference to `extcon_get_state'
vim +2405 drivers/gpu/drm/bridge/sil-sii8620.c
ce6e153f Andrzej Hajda 2016-10-10 2399
ce6e153f Andrzej Hajda 2016-10-10 2400 static int sii8620_remove(struct i2c_client *client)
ce6e153f Andrzej Hajda 2016-10-10 2401 {
ce6e153f Andrzej Hajda 2016-10-10 2402 struct sii8620 *ctx = i2c_get_clientdata(client);
ce6e153f Andrzej Hajda 2016-10-10 2403
68883844 Maciej Purski 2018-02-27 2404 if (ctx->extcon) {
68883844 Maciej Purski 2018-02-27 @2405 extcon_unregister_notifier(ctx->extcon, EXTCON_DISP_MHL,
68883844 Maciej Purski 2018-02-27 2406 &ctx->extcon_nb);
68883844 Maciej Purski 2018-02-27 2407 flush_work(&ctx->extcon_wq);
68883844 Maciej Purski 2018-02-27 2408 if (ctx->cable_state > 0)
68883844 Maciej Purski 2018-02-27 2409 sii8620_cable_out(ctx);
68883844 Maciej Purski 2018-02-27 2410 } else {
68883844 Maciej Purski 2018-02-27 2411 sii8620_cable_out(ctx);
68883844 Maciej Purski 2018-02-27 2412 }
e25f1f7c Maciej Purski 2017-08-24 2413 drm_bridge_remove(&ctx->bridge);
ce6e153f Andrzej Hajda 2016-10-10 2414
ce6e153f Andrzej Hajda 2016-10-10 2415 return 0;
ce6e153f Andrzej Hajda 2016-10-10 2416 }
ce6e153f Andrzej Hajda 2016-10-10 2417
:::::: The code at line 2405 was first introduced by commit
:::::: 688838442147d9dd94c2ef7c2c31a35cf150c5fa drm/bridge/sii8620: use micro-USB cable detection logic to detect MHL
:::::: TO: Maciej Purski <m.purski@samsung.com>
:::::: CC: Chanwoo Choi <cw00.choi@samsung.com>
---
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: 30004 bytes --]
next reply other threads:[~2018-05-04 17:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 17:57 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-04-29 3:15 kbuild test robot
2018-04-30 18:23 ` Randy Dunlap
[not found] <CGME20180406095349epcas2p22b69ac92909aeddc04a4e7a4f3c64c3f@epcas2p2.samsung.com>
2018-04-06 9:52 ` kbuild test robot
2018-04-06 10:14 ` Andrzej Hajda
2018-04-06 10:34 ` Chanwoo Choi
2018-04-06 13:55 ` Andrzej Hajda
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=201805050142.teMqO83j%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=brgl@bgdev.pl \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--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®