Hi Ville,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on drm-intel/for-linux-next
drm-intel/for-linux-next-fixes drm-tip/drm-tip linus/master v6.9-rc2
next-20240405]
[If your patch is applied to the wrong git
Hey,
On 2024-04-05 15:36, Lucas De Marchi wrote:
what does "rebase" instead of "PATCH" is supposed to mean here?
And then we have a "PATCH v2" as reply to this one.
Shouldn't this go to dri-devel (too)?
Lucas De Marchi
I was rebasing so no changes were originally made.
Afterwards I found
== Series Details ==
Series: drm/i915/guc: Update w/a 14019159160 (rev3)
URL : https://patchwork.freedesktop.org/series/130890/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_14538 -> Patchwork_130890v3
Summary
---
== Series Details ==
Series: drm/i915/guc: Update w/a 14019159160 (rev3)
URL : https://patchwork.freedesktop.org/series/130890/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
== Series Details ==
Series: drm/i915/guc: Update w/a 14019159160 (rev3)
URL : https://patchwork.freedesktop.org/series/130890/
State : warning
== Summary ==
Error: dim checkpatch failed
dce5a13e42cb drm/i915/guc: Update w/a 14019159160
-:20: WARNING:LONG_LINE_COMMENT: line length of 108
