Re: [kbuild-all] [PATCH 1/2] usb: phy: Introduce one extcon device into usb phy

[Baolin Wang]

Hi,

On 22 March 2017 at 14:32, Ye Xiaolong <xiaolong.ye@xxxxxxxxx> wrote:
> On 03/20, Baolin Wang wrote:
>>Hi,
>>
>>
>>On 19 March 2017 at 19:42, kbuild test robot <lkp@xxxxxxxxx> wrote:
>>> Hi Baolin,
>>>
>>> [auto build test ERROR on balbi-usb/next]
>>> [also build test ERROR on v4.11-rc2 next-20170310]
>>> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>>>
>>> url:    https://github.com/0day-ci/linux/commits/Baolin-Wang/usb-phy-Introduce-one-extcon-device-into-usb-phy/20170319-175509
>>> base:   https://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git next
>>> config: i386-randconfig-i1-201712 (attached as .config)
>>> compiler: gcc-4.8 (Debian 4.8.4-1) 4.8.4
>>> reproduce:
>>>         # save the attached .config to linux build tree
>>>         make ARCH=i386
>>>
>>> All errors (new ones prefixed by >>):
>>>
>>>    drivers/built-in.o: In function `usb_add_extcon':
>>>>> phy.c:(.text+0x231580): undefined reference to `extcon_get_edev_by_phandle'
>>>>> phy.c:(.text+0x2315d0): undefined reference to `devm_extcon_register_notifier'
>>>    phy.c:(.text+0x231629): undefined reference to `devm_extcon_register_notifier'
>>
>>I am not sure how the errors were happened, since we will always
>>select EXTCON if we have selected USB_PHY, moreover we have included
>
> Hmm, this was a random config test and CONFIG_EXTCON was set as 'm', maybe you
> need to specify the dependency between CONFIG_USB_PHY and CONFIG_EXTCON ?

OK, I see. Thanks.

-- 
Baolin.wang
Best Regards