All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Masney <bmasney@redhat.com>
To: kbuild-all@lists.01.org
Subject: Re: [linux-next:master 3267/10468] drm_dp_mst_topology.c:undefined reference to `__drm_atomic_helper_private_obj_duplicate_state'
Date: Wed, 16 Mar 2022 12:07:03 -0400	[thread overview]
Message-ID: <YjILJ2iamv/JE8+f@x1> (raw)
In-Reply-To: <47d7f15e-7f6c-2fb5-f5dc-b059213fb69e@suse.de>

[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]

On Mon, Mar 14, 2022 at 08:05:37PM +0100, Thomas Zimmermann wrote:
> Hi
> 
> Am 04.03.22 um 21:26 schrieb Lyude Paul:
> > Thomas, I assume this is on your radar?
> 
> Yes, it is. I just need to reproduce the problem. I think we have to select
> DRM_KMS_HELPER from DRM_PANEL_EDP.

I am encountering this issue on linux-next-20220316 when
building 'make qcom_defconfig' on arm32. I selected DRM_KMS_HELPER in
DRM_PANEL_EDP and that fails with the following error:

    Running 'make qcom_defconfig'
    drivers/gpu/drm/panel/Kconfig:2:error: recursive dependency detected!
    drivers/gpu/drm/panel/Kconfig:2:	symbol DRM_PANEL is selected by DRM_PANEL_BRIDGE
    drivers/gpu/drm/bridge/Kconfig:8:	symbol DRM_PANEL_BRIDGE depends on DRM_KMS_HELPER
    drivers/gpu/drm/Kconfig:91:	symbol DRM_KMS_HELPER is selected by DRM_PANEL_EDP
    drivers/gpu/drm/panel/Kconfig:102:	symbol DRM_PANEL_EDP depends on DRM_PANEL
    For a resolution refer to Documentation/kbuild/kconfig-language.rst
    subsection "Kconfig recursive dependency limitations"

Brian

WARNING: multiple messages have this Message-ID (diff)
From: Brian Masney <bmasney@redhat.com>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: Lyude Paul <lyude@redhat.com>, kernel test robot <lkp@intel.com>,
	kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 3267/10468] drm_dp_mst_topology.c:undefined reference to `__drm_atomic_helper_private_obj_duplicate_state'
Date: Wed, 16 Mar 2022 12:07:03 -0400	[thread overview]
Message-ID: <YjILJ2iamv/JE8+f@x1> (raw)
In-Reply-To: <47d7f15e-7f6c-2fb5-f5dc-b059213fb69e@suse.de>

On Mon, Mar 14, 2022 at 08:05:37PM +0100, Thomas Zimmermann wrote:
> Hi
> 
> Am 04.03.22 um 21:26 schrieb Lyude Paul:
> > Thomas, I assume this is on your radar?
> 
> Yes, it is. I just need to reproduce the problem. I think we have to select
> DRM_KMS_HELPER from DRM_PANEL_EDP.

I am encountering this issue on linux-next-20220316 when
building 'make qcom_defconfig' on arm32. I selected DRM_KMS_HELPER in
DRM_PANEL_EDP and that fails with the following error:

    Running 'make qcom_defconfig'
    drivers/gpu/drm/panel/Kconfig:2:error: recursive dependency detected!
    drivers/gpu/drm/panel/Kconfig:2:	symbol DRM_PANEL is selected by DRM_PANEL_BRIDGE
    drivers/gpu/drm/bridge/Kconfig:8:	symbol DRM_PANEL_BRIDGE depends on DRM_KMS_HELPER
    drivers/gpu/drm/Kconfig:91:	symbol DRM_KMS_HELPER is selected by DRM_PANEL_EDP
    drivers/gpu/drm/panel/Kconfig:102:	symbol DRM_PANEL_EDP depends on DRM_PANEL
    For a resolution refer to Documentation/kbuild/kconfig-language.rst
    subsection "Kconfig recursive dependency limitations"

Brian



  reply	other threads:[~2022-03-16 16:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-04  2:47 [linux-next:master 3267/10468] drm_dp_mst_topology.c:undefined reference to `__drm_atomic_helper_private_obj_duplicate_state' kernel test robot
2022-03-04 20:26 ` Lyude Paul
2022-03-04 20:26   ` Lyude Paul
2022-03-14 19:05   ` Thomas Zimmermann
2022-03-14 19:05     ` Thomas Zimmermann
2022-03-16 16:07     ` Brian Masney [this message]
2022-03-16 16:07       ` Brian Masney
2022-03-16 19:08       ` Thomas Zimmermann
2022-03-16 19:08         ` Thomas Zimmermann

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=YjILJ2iamv/JE8+f@x1 \
    --to=bmasney@redhat.com \
    --cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.