Reporting (or not reporting) drm test build failures

Guenter Roeck linux at roeck-us.net
Sat Mar 16 16:57:10 UTC 2024


Hi,

recently there was a suggestion that drm build tests on architectures
such as xtensa should not happen or not be reported. The current mainline
kernel experiences a number of drm related build failures.

Building csky:allmodconfig ... failed
--------------
Error log:
ERROR: modpost: "__udivdi3" [drivers/gpu/drm/sun4i/sun4i-drm-hdmi.ko] undefined!
make[3]: [scripts/Makefile.modpost:145: Module.symvers] Error 1 (ignored)

[ also seen with xtensa]

Building mips:allmodconfig ... failed
--------------
Error log:
drivers/gpu/drm/xe/xe_lrc.c:100: error: "END" redefined

I really don't want to waste people's time if reporting such problems
is considered noise/nuisance. Is there some guidance available explaining
which architectures and/or platforms are "fair game" for drm build tests,
or, better, which platforms/architectures should explicitly _not_ build
test the drm subsystem ?

Thanks,
Guenter


More information about the dri-devel mailing list