mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Andrzej Hajda <a.hajda@samsung.com>,
	kbuild test robot <lkp@intel.com>,
	Maciej Purski <m.purski@samsung.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	Chanwoo Choi <cw00.choi@samsung.com>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Archit Taneja <architt@codeaurora.org>,
	Laurent Pinchart <Laurent.pinchart@ideasonboard.com>
Subject: Re: drivers/gpu/drm/bridge/sil-sii8620.c:2229: undefined reference to `extcon_find_edev_by_node'
Date: Mon, 7 May 2018 09:36:49 -0700	[thread overview]
Message-ID: <b1fd759a-5cea-0bdd-87d1-601cdc68f335@infradead.org> (raw)
In-Reply-To: <d429947c-e238-da71-94ab-022af0972b46@infradead.org>

On 05/07/2018 09:13 AM, Randy Dunlap wrote:
> On 05/07/2018 12:09 AM, Andrzej Hajda wrote:
>> On 06.05.2018 02:46, Randy Dunlap wrote:
>>> On 05/05/2018 04:22 PM, kbuild test robot wrote:
>>>> Hi Maciej,
>>>>
>>>> FYI, the error/warning still remains.
>>> Hi M. Robot,
>>>
>>> I am cc-ing dri-devel@lists.freedesktop.org so that they are aware of the
>>> multiple times that you have posted this kbuild error (I have 3 different
>>> posts in my Inbox with the same errors; I may have missed some).
>>>
>>> I hope that someone there will have some insights into this problem.
>>>
>>> I have looked at the issues and concluded that the correct fix for this IMO is:
>>>
>>> config DRM_SIL_SII8620
>>> ...
>>> 	depends on EXTCON || !EXTCON
>>>
>>> However, that causes some unhappy errors from scripts/kconfig/ concerning
>>> Kconfig recursive dependencies detected.  Alternatively, using
>>> 	select EXTCON
>>> does not cause any kconfig recursive dependency issues and solves the build
>>> errors.
>>>
>>>
>>> thanks!
>>
>>
>> Hi Randy,
>>
>> Proper patch was posted some times ago[1], and it was merged today to
>> drm-misc-fixes branch.
>>
>> [1]: https://patchwork.kernel.org/patch/10330653/
>>
>>
>> Regards
>> Andrzej
> 
> Thank you for the info.

and
Tested-by: Randy Dunlap <rdunlap@infradead.org>

-- 
~Randy

      reply	other threads:[~2018-05-07 16:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-05 23:22 kbuild test robot
2018-05-06  0:46 ` Randy Dunlap
2018-05-07  7:09   ` Andrzej Hajda
2018-05-07 16:13     ` Randy Dunlap
2018-05-07 16:36       ` Randy Dunlap [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=b1fd759a-5cea-0bdd-87d1-601cdc68f335@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=a.hajda@samsung.com \
    --cc=architt@codeaurora.org \
    --cc=cw00.choi@samsung.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=m.purski@samsung.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®