public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kishon Vijay Abraham I <kishon@ti.com>
To: Stephen Boyd <stephen.boyd@linaro.org>,
	kbuild test robot <fengguang.wu@intel.com>
Cc: <kbuild-all@01.org>, <linux-kernel@vger.kernel.org>
Subject: Re: phy-qcom-usb-hs.c:undefined reference to `extcon_unregister_notifier'
Date: Thu, 9 Mar 2017 13:46:24 +0530	[thread overview]
Message-ID: <58C10F58.3070908@ti.com> (raw)
In-Reply-To: <148890248349.8530.6424318650202045981@sboyd-linaro>



On Tuesday 07 March 2017 09:31 PM, Stephen Boyd wrote:
> Quoting kbuild test robot (2017-03-06 09:19:50)
>> 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'
> 
> Agreed. The same fix is required:
> 
> ----8<-----
> From: Stephen Boyd <stephen.boyd@linaro.org>
> Subject: [PATCH] phy: qcom-usb-hs: Add depends on EXTCON
> 
> We get the following compile errors if EXTCON is enabled as a
> module but this driver is builtin:
> 
> drivers/built-in.o: In function `qcom_usb_hs_phy_power_off':
> phy-qcom-usb-hs.c:(.text+0x1089): undefined reference to `extcon_unregister_notifier'
> drivers/built-in.o: In function `qcom_usb_hs_phy_probe':
> phy-qcom-usb-hs.c:(.text+0x11b5): undefined reference to `extcon_get_edev_by_phandle'
> drivers/built-in.o: In function `qcom_usb_hs_phy_power_on':
> phy-qcom-usb-hs.c:(.text+0x128e): undefined reference to `extcon_get_state'
> phy-qcom-usb-hs.c:(.text+0x12a9): undefined reference to `extcon_register_notifier'
> 
> so let's mark this as needing to follow the modular status of
> the extcon framework.
> 
> Fixes: 9994a33865f4 e2427b09ba929c2b9 (phy: Add support for Qualcomm's USB HS phy")
> Signed-off-by: Stephen Boyd <stephen.boyd@linaro.org>

merged, thanks.

-Kishon

> ---
>  drivers/phy/Kconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/phy/Kconfig b/drivers/phy/Kconfig
> index 61a22e985831..0386534892c5 100644
> --- a/drivers/phy/Kconfig
> +++ b/drivers/phy/Kconfig
> @@ -440,6 +440,7 @@ config PHY_QCOM_UFS
>  config PHY_QCOM_USB_HS
>  	tristate "Qualcomm USB HS PHY module"
>  	depends on USB_ULPI_BUS
> +	depends on EXTCON || !EXTCON # if EXTCON=m, this cannot be built-in
>  	select GENERIC_PHY
>  	help
>  	  Support for the USB high-speed ULPI compliant phy on Qualcomm
> 

      reply	other threads:[~2017-03-09  8:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-06 17:19 phy-qcom-usb-hs.c:undefined reference to `extcon_unregister_notifier' kbuild test robot
2017-03-07 16:01 ` Stephen Boyd
2017-03-09  8:16   ` Kishon Vijay Abraham I [this message]

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=58C10F58.3070908@ti.com \
    --to=kishon@ti.com \
    --cc=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --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