From: kernel test robot <lkp@intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
dri-devel@lists.freedesktop.org
Cc: oe-kbuild-all@lists.linux.dev, intel-gfx@lists.freedesktop.org,
intel-xe@lists.freedesktop.org,
Maxime Ripard <mripard@kernel.org>
Subject: Re: [PATCH] drm/client: Build the tests with CONFIG_DRM_KUNIT_TEST=m
Date: Mon, 3 Mar 2025 21:41:15 +0800 [thread overview]
Message-ID: <202503032114.TQkZ0b7R-lkp@intel.com> (raw)
In-Reply-To: <20250303094808.11860-1-ville.syrjala@linux.intel.com>
Hi Ville,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-exynos/exynos-drm-next]
[also build test ERROR on linus/master v6.14-rc5]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Ville-Syrjala/drm-client-Build-the-tests-with-CONFIG_DRM_KUNIT_TEST-m/20250303-175715
base: https://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git exynos-drm-next
patch link: https://lore.kernel.org/r/20250303094808.11860-1-ville.syrjala%40linux.intel.com
patch subject: [PATCH] drm/client: Build the tests with CONFIG_DRM_KUNIT_TEST=m
config: riscv-randconfig-002-20250303 (https://download.01.org/0day-ci/archive/20250303/202503032114.TQkZ0b7R-lkp@intel.com/config)
compiler: riscv32-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250303/202503032114.TQkZ0b7R-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202503032114.TQkZ0b7R-lkp@intel.com/
All errors (new ones prefixed by >>):
riscv32-linux-ld: drivers/gpu/drm/drm_client_modeset.o: in function `drm_client_modeset_test_init':
>> drivers/gpu/drm/tests/drm_client_modeset_test.c:59:(.text.drm_client_modeset_test_init+0xa4): undefined reference to `drm_kunit_helper_alloc_device'
riscv32-linux-ld: drivers/gpu/drm/drm_client_modeset.o: in function `__drm_kunit_helper_alloc_drm_device':
>> include/drm/drm_kunit_helpers.h:63:(.text.drm_client_modeset_test_init+0x198): undefined reference to `__drm_kunit_helper_alloc_drm_device_with_driver'
vim +59 drivers/gpu/drm/tests/drm_client_modeset_test.c
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 52
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 53 static int drm_client_modeset_test_init(struct kunit *test)
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 54 {
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 55 struct drm_client_modeset_test_priv *priv;
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 56 int ret;
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 57
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 58 priv = kunit_kzalloc(test, sizeof(*priv), GFP_KERNEL);
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 @59 KUNIT_ASSERT_NOT_NULL(test, priv);
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 60
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 61 test->priv = priv;
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 62
9ecd8045bf64f8 Maxime Ripard 2022-12-01 63 priv->dev = drm_kunit_helper_alloc_device(test);
9ecd8045bf64f8 Maxime Ripard 2022-12-01 64 KUNIT_ASSERT_NOT_ERR_OR_NULL(test, priv->dev);
9ecd8045bf64f8 Maxime Ripard 2022-12-01 65
a9143c5852a7a1 Maxime Ripard 2022-12-01 66 priv->drm = __drm_kunit_helper_alloc_drm_device(test, priv->dev,
a9143c5852a7a1 Maxime Ripard 2022-12-01 67 sizeof(*priv->drm), 0,
a9143c5852a7a1 Maxime Ripard 2022-12-01 68 DRIVER_MODESET);
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 69 KUNIT_ASSERT_NOT_ERR_OR_NULL(test, priv->drm);
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 70
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 71 ret = drmm_connector_init(priv->drm, &priv->connector,
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 72 &drm_client_modeset_connector_funcs,
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 73 DRM_MODE_CONNECTOR_Unknown,
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 74 NULL);
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 75 KUNIT_ASSERT_EQ(test, ret, 0);
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 76
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 77 drm_connector_helper_add(&priv->connector, &drm_client_modeset_connector_helper_funcs);
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 78
fedcaf726f542b Maxime Ripard 2022-11-17 79 priv->connector.interlace_allowed = true;
fedcaf726f542b Maxime Ripard 2022-11-17 80 priv->connector.doublescan_allowed = true;
fedcaf726f542b Maxime Ripard 2022-11-17 81
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 82 return 0;
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 83 }
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 84
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-03-03 13:42 UTC|newest]
Thread overview: 10+ 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 9:53 ` ✓ CI.Patch_applied: success for " Patchwork
2025-03-03 9:53 ` ✓ CI.checkpatch: " Patchwork
2025-03-03 9:54 ` ✓ CI.KUnit: " Patchwork
2025-03-03 10:02 ` ✗ CI.Build: failure " Patchwork
2025-03-03 12:28 ` Ville Syrjälä
2025-03-07 3:04 ` Lucas De Marchi
2025-03-03 11:03 ` [PATCH] " Jani Nikula
2025-03-03 12:06 ` Maxime Ripard
2025-03-03 13:41 ` kernel test robot [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=202503032114.TQkZ0b7R-lkp@intel.com \
--to=lkp@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=mripard@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ville.syrjala@linux.intel.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