Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Message-ID: <5DF209E3.2080808@huawei.com>
Date:   Thu, 12 Dec 2019 17:35:31 +0800
From:   zhong jiang <zhongjiang@huawei.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To:     Greg KH <gregkh@linuxfoundation.org>
CC:     Heikki Krogerus <heikki.krogerus@linux.intel.com>,
        <linux@roeck-us.net>, <linux-usb@vger.kernel.org>,
        <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] usb: typec: fusb302: Fix an undefined reference to 'extcon_get_state'
References: <1576136063-50916-1-git-send-email-zhongjiang@huawei.com> <20191212090132.GC31345@kuha.fi.intel.com> <5DF20530.2040509@huawei.com> <20191212092805.GA1375559@kroah.com>
In-Reply-To: <20191212092805.GA1375559@kroah.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On 2019/12/12 17:28, Greg KH wrote:
> On Thu, Dec 12, 2019 at 05:15:28PM +0800, zhong jiang wrote:
>> On 2019/12/12 17:01, Heikki Krogerus wrote:
>>> On Thu, Dec 12, 2019 at 03:34:23PM +0800, zhong jiang wrote:
>>>> Fixes the following compile error:
>>>>
>>>> drivers/usb/typec/tcpm/fusb302.o: In function `tcpm_get_current_limit':
>>>> fusb302.c:(.text+0x3ee): undefined reference to `extcon_get_state'
>>>> fusb302.c:(.text+0x422): undefined reference to `extcon_get_state'
>>>> fusb302.c:(.text+0x450): undefined reference to `extcon_get_state'
>>>> fusb302.c:(.text+0x48c): undefined reference to `extcon_get_state'
>>>> drivers/usb/typec/tcpm/fusb302.o: In function `fusb302_probe':
>>>> fusb302.c:(.text+0x980): undefined reference to `extcon_get_extcon_dev'
>>>> make: *** [vmlinux] Error 1
>>> There are stubs for those functions so that really should not be
>>> happening. I can not reproduce that.
>> It can be reproduced in next branch. you can try it in the latest next branch.
> Can it be reproduced in 5.5-rc1?
Yes
> .
>