mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Baolin Wang <baolin.wang@linaro.org>
Cc: kbuild test robot <lkp@intel.com>,
	Felipe Balbi <balbi@kernel.org>,
	Linaro Kernel Mailman List <linaro-kernel@lists.linaro.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	USB <linux-usb@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>, NeilBrown <neilb@suse.com>,
	Mark Brown <broonie@kernel.org>,
	kbuild-all@01.org, Peter Chen <peter.chen@freescale.com>,
	Jun Li <jun.li@nxp.com>
Subject: Re: [kbuild-all] [PATCH 1/2] usb: phy: Introduce one extcon device into usb phy
Date: Wed, 22 Mar 2017 14:32:11 +0800	[thread overview]
Message-ID: <20170322063211.GA5245@yexl-desktop> (raw)
In-Reply-To: <CAMz4kuLZfLHGtStHDDo=7K54K60peEZ6FKq21ksgiamvhBsX0w@mail.gmail.com>

On 03/20, Baolin Wang wrote:
>Hi,
>
>
>On 19 March 2017 at 19:42, kbuild test robot <lkp@intel.com> 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 ?

Thanks,
Xiaolong

>the "linux/extcon.h" in phy.h file.
>
>-- 
>Baolin.wang
>Best Regards
>_______________________________________________
>kbuild-all mailing list
>kbuild-all@lists.01.org
>https://lists.01.org/mailman/listinfo/kbuild-all

  reply	other threads:[~2017-03-22  6:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-17  6:19 Baolin Wang
2017-03-17  6:19 ` [PATCH 2/2] usb: phy: phy-qcom-8x16-usb: Remove redundant extcon register/unregister Baolin Wang
2017-03-19 11:42 ` [PATCH 1/2] usb: phy: Introduce one extcon device into usb phy kbuild test robot
2017-03-20  8:30   ` Baolin Wang
2017-03-22  6:32     ` Ye Xiaolong [this message]
2017-03-22  6:48       ` [kbuild-all] " Baolin Wang

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=20170322063211.GA5245@yexl-desktop \
    --to=xiaolong.ye@intel.com \
    --cc=balbi@kernel.org \
    --cc=baolin.wang@linaro.org \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jun.li@nxp.com \
    --cc=kbuild-all@01.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=neilb@suse.com \
    --cc=peter.chen@freescale.com \
    /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®