From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Maxime Ripard <mripard@kernel.org>, dri-devel@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BUILD: failure for drm/client: Build the tests with CONFIG_DRM_KUNIT_TEST=m
Date: Mon, 3 Mar 2025 14:26:47 +0200 [thread overview]
Message-ID: <Z8WgBx5sVVcoLYsk@intel.com> (raw)
In-Reply-To: <174100275212.118223.16006543455148366118@b555e5b46a47>
On Mon, Mar 03, 2025 at 11:52:32AM -0000, Patchwork wrote:
> == Series Details ==
>
> Series: drm/client: Build the tests with CONFIG_DRM_KUNIT_TEST=m
> URL : https://patchwork.freedesktop.org/series/145707/
> State : failure
>
> == Summary ==
>
> Error: make failed
> CALL scripts/checksyscalls.sh
> DESCEND objtool
> INSTALL libsubcmd_headers
> CHK kernel/kheaders_data.tar.xz
> HDRTEST drivers/gpu/drm/xe/generated/xe_wa_oob.h
> UPD include/generated/utsversion.h
> CC init/version-timestamp.o
> KSYMS .tmp_vmlinux0.kallsyms.S
> AS .tmp_vmlinux0.kallsyms.o
> LD .tmp_vmlinux1
> ld: drivers/gpu/drm/drm_client_modeset.o: in function `drm_test_pick_cmdline_named':
> /home/kbuild/kernel/drivers/gpu/drm/tests/drm_client_modeset_test.c:142:(.text+0x3c9): undefined reference to `drm_helper_probe_single_connector_modes'
That comes from drm_kms_helper.ko, but drm_client* goes into
drm.ko. So this looks like a circular dependency :/
> ld: /home/kbuild/kernel/drivers/gpu/drm/tests/drm_client_modeset_test.c:136:(.text+0x4b1): undefined reference to `kunit_unary_assert_format'
No idea what is going on with these. Should be coming via CONFIG_KUNT
and we do seem to depend on that.
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2025-03-03 12:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 9:48 [PATCH] drm/client: Build the tests with CONFIG_DRM_KUNIT_TEST=m Ville Syrjala
2025-03-03 11:03 ` Jani Nikula
2025-03-03 11:52 ` ✗ Fi.CI.BUILD: failure for " Patchwork
2025-03-03 12:26 ` Ville Syrjälä [this message]
2025-03-03 12:06 ` [PATCH] " Maxime Ripard
2025-03-03 13:41 ` kernel test robot
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=Z8WgBx5sVVcoLYsk@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mripard@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox