On 11/02/2026 10:56, Philipp Stanner wrote:
On Thu, 2026-01-29 at 23:31 +0800, kernel test robot wrote:
Hi Tvrtko,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on drm-xe/drm-xe-next daeinki-drm-exynos/exynos-drm-next
drm/drm-next drm-i915/for-linux-next drm-i915/for-linux-next-fixes
drm-tip/drm-tip linus/master v6.19-rc7 next-20260128]
[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]
Hi Tvrtko,
what about this build error? Seems to be an Xe branch conflict?
I don't know what happened there in LKP, it appeared for the first time
with v6. Drm_sched_scheduler_two_clients_attr looks constant to me:
static const struct kunit_attributes
drm_sched_scheduler_two_clients_attr = {
.speed = KUNIT_SPEED_SLOW,
};
static struct kunit_case drm_sched_scheduler_two_clients_tests[] = {
KUNIT_CASE_PARAM_ATTR(drm_sched_scheduler_two_clients_test,
drm_sched_scheduler_two_clients_gen_params,
drm_sched_scheduler_two_clients_attr),
{}
};
It builds fine for me but I will keep an eye on it.
BTW, I think Danilo and I told you a few times already that we would
like to get the whole patch series into our inboxes. You seem to
exclude patches for other components, but it's important for me to see
all the other driver maintainers' RBs etc. there and be easily able to
ping those who haven't reacted yet and so on. Also quickly coyping an
mbox to test-apply something etc. etc. is easier
I guess you want to spare people from noisy mail traffic, but getting
31 patches is not a problem, those who don't care can simple ignore
them or collapse the thread in their mail program and so on.
I assume all important people are subscribed to dri-devel anyway so all
patches should be in their inboxes. But I will try and remember to
explicitly cc you two.
Regards,
Tvrtko
url:
https://github.com/intel-lab-lkp/linux/commits/Tvrtko-Ursulin/drm-amdgpu-Reject-impossible-entities-early/20260128-191117
base: https://gitlab.freedesktop.org/drm/misc/kernel.git drm-misc-next
patch link:
https://lore.kernel.org/r/20260128110806.38350-7-tvrtko.ursulin%40igalia.com
patch subject: [PATCH v6 06/31] drm/sched: Add some scheduling quality unit
tests
config: riscv-allyesconfig
(https://download.01.org/0day-ci/archive/20260129/[email protected]/config)
compiler: clang version 16.0.6 (https://github.com/llvm/llvm-project
7cbf1a2591520c2491aa35339f227775f4d3adf6)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20260129/[email protected]/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 <[email protected]>
Closes:
https://lore.kernel.org/oe-kbuild-all/[email protected]/
All errors (new ones prefixed by >>):
drivers/gpu/drm/scheduler/tests/tests_scheduler.c:676:10: error: initializer
element is not a compile-time constant
drm_sched_scheduler_two_clients_attr),
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/kunit/test.h:224:13: note: expanded from macro
'KUNIT_CASE_PARAM_ATTR'
.attr = attributes, .module_name = KBUILD_MODNAME}
^~~~~~~~~~
1 error generated.
vim +676 drivers/gpu/drm/scheduler/tests/tests_scheduler.c
672
673 static struct kunit_case drm_sched_scheduler_two_clients_tests[] = {
674 KUNIT_CASE_PARAM_ATTR(drm_sched_scheduler_two_clients_test,
675
drm_sched_scheduler_two_clients_gen_params,
> 676
drm_sched_scheduler_two_clients_attr),
677 {}
678 };
679
