From: kbuild test robot <fengguang.wu@intel.com>
To: Stephen Boyd <stephen.boyd@linaro.org>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Kishon Vijay Abraham I <kishon@ti.com>
Subject: phy-qcom-usb-hs.c:undefined reference to `extcon_unregister_notifier'
Date: Tue, 7 Mar 2017 01:19:50 +0800 [thread overview]
Message-ID: <201703070147.dKzorjbl%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]
Hi Stephen,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: c1ae3cfa0e89fa1a7ecc4c99031f5e9ae99d9201
commit: e2427b09ba929c2b9d02556b74a85161a7364792 phy: Add support for Qualcomm's USB HS phy
date: 5 weeks ago
config: i386-randconfig-x019-03061728 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
git checkout e2427b09ba929c2b9d02556b74a85161a7364792
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
drivers/built-in.o: In function `qcom_usb_hs_phy_power_off':
>> phy-qcom-usb-hs.c:(.text+0x1248): undefined reference to `extcon_unregister_notifier'
drivers/built-in.o: In function `qcom_usb_hs_phy_power_on':
>> phy-qcom-usb-hs.c:(.text+0x1389): undefined reference to `extcon_get_state'
>> phy-qcom-usb-hs.c:(.text+0x13a4): undefined reference to `extcon_register_notifier'
drivers/built-in.o: In function `qcom_usb_hs_phy_probe':
>> phy-qcom-usb-hs.c:(.text+0x1551): undefined reference to `extcon_get_edev_by_phandle'
---
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: 31482 bytes --]
next reply other threads:[~2017-03-06 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 17:19 kbuild test robot [this message]
2017-03-07 16:01 ` phy-qcom-usb-hs.c:undefined reference to `extcon_unregister_notifier' Stephen Boyd
2017-03-09 8:16 ` Kishon Vijay Abraham I
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=201703070147.dKzorjbl%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stephen.boyd@linaro.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).