From: Linus Walleij <linus.walleij@linaro.org>
To: Doug Anderson <dianders@chromium.org>
Cc: "kernel test robot" <lkp@intel.com>,
llvm@lists.linux.dev, kbuild-all@lists.01.org,
LKML <linux-kernel@vger.kernel.org>,
"Noralf Trønnes" <noralf@tronnes.org>
Subject: Re: ld.lld: error: undefined symbol: drm_gem_fb_get_obj
Date: Fri, 26 Aug 2022 21:59:34 +0200 [thread overview]
Message-ID: <CACRpkdaK+8bropqoRCaEw6KH7ZKRHUwNBPtc-cOojJZt+3S+yw@mail.gmail.com> (raw)
In-Reply-To: <CAD=FV=Vxdoo21OQJ-Ad57-gFVcJ7biQipoJqDE2bSpLC2NxrhQ@mail.gmail.com>
On Fri, Aug 26, 2022 at 5:48 PM Doug Anderson <dianders@chromium.org> wrote:
> Unfortunately, fixing the error isn't the most trivial thing in the
> world. If you just do this:
>
> config DRM_MIPI_DBI
> tristate
> + select DRM_KMS_HELPER
> depends on DRM
>
> ...then you get a circular dependency:
>
> drivers/gpu/drm/Kconfig:76:error: recursive dependency detected!
> drivers/gpu/drm/Kconfig:76: symbol DRM_KMS_HELPER is selected by
> DRM_MIPI_DBI
> drivers/gpu/drm/Kconfig:31: symbol DRM_MIPI_DBI is selected by
> DRM_PANEL_ILITEK_ILI9341
> drivers/gpu/drm/panel/Kconfig:165: symbol
> DRM_PANEL_ILITEK_ILI9341 depends on DRM_KMS_HELPER
> For a resolution refer to Documentation/kbuild/kconfig-language.rst
> subsection "Kconfig recursive dependency limitations"
It turns out Randy Dunlap had made the right fixes, and I merged them
before you got the chance to reply!
https://cgit.freedesktop.org/drm/drm-misc/commit/?id=84dfc46594b0167e5d3736273b0e0e05365da641
https://cgit.freedesktop.org/drm/drm-misc/commit/?id=eb7de496451bd969e203f02f66585131228ba4ae
But thanks!
Yours,
Linus Walleij
WARNING: multiple messages have this Message-ID (diff)
From: Linus Walleij <linus.walleij@linaro.org>
To: kbuild-all@lists.01.org
Subject: Re: ld.lld: error: undefined symbol: drm_gem_fb_get_obj
Date: Fri, 26 Aug 2022 21:59:34 +0200 [thread overview]
Message-ID: <CACRpkdaK+8bropqoRCaEw6KH7ZKRHUwNBPtc-cOojJZt+3S+yw@mail.gmail.com> (raw)
In-Reply-To: <CAD=FV=Vxdoo21OQJ-Ad57-gFVcJ7biQipoJqDE2bSpLC2NxrhQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]
On Fri, Aug 26, 2022 at 5:48 PM Doug Anderson <dianders@chromium.org> wrote:
> Unfortunately, fixing the error isn't the most trivial thing in the
> world. If you just do this:
>
> config DRM_MIPI_DBI
> tristate
> + select DRM_KMS_HELPER
> depends on DRM
>
> ...then you get a circular dependency:
>
> drivers/gpu/drm/Kconfig:76:error: recursive dependency detected!
> drivers/gpu/drm/Kconfig:76: symbol DRM_KMS_HELPER is selected by
> DRM_MIPI_DBI
> drivers/gpu/drm/Kconfig:31: symbol DRM_MIPI_DBI is selected by
> DRM_PANEL_ILITEK_ILI9341
> drivers/gpu/drm/panel/Kconfig:165: symbol
> DRM_PANEL_ILITEK_ILI9341 depends on DRM_KMS_HELPER
> For a resolution refer to Documentation/kbuild/kconfig-language.rst
> subsection "Kconfig recursive dependency limitations"
It turns out Randy Dunlap had made the right fixes, and I merged them
before you got the chance to reply!
https://cgit.freedesktop.org/drm/drm-misc/commit/?id=84dfc46594b0167e5d3736273b0e0e05365da641
https://cgit.freedesktop.org/drm/drm-misc/commit/?id=eb7de496451bd969e203f02f66585131228ba4ae
But thanks!
Yours,
Linus Walleij
next prev parent reply other threads:[~2022-08-26 19:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 7:26 ld.lld: error: undefined symbol: drm_gem_fb_get_obj kernel test robot
2022-08-26 8:26 ` Linus Walleij
2022-08-26 8:26 ` Linus Walleij
2022-08-26 15:48 ` Doug Anderson
2022-08-26 15:48 ` Doug Anderson
2022-08-26 19:59 ` Linus Walleij [this message]
2022-08-26 19:59 ` Linus Walleij
2022-08-26 15:59 ` Nathan Chancellor
2022-08-26 15:59 ` Nathan Chancellor
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=CACRpkdaK+8bropqoRCaEw6KH7ZKRHUwNBPtc-cOojJZt+3S+yw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=dianders@chromium.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=noralf@tronnes.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.