Re: [Intel-gfx] [PATCH] drm/i915/kbl: Fix revision ID checks

Hi Matt, Thank you for the patch! Yet something to improve: [auto build test ERROR on drm-intel/for-linux-next] [also build test ERROR on drm-tip/drm-tip next-20200807] [cannot apply to v5.8] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/kbl: Fix revision ID checks

== Series Details == Series: drm/i915/kbl: Fix revision ID checks URL : https://patchwork.freedesktop.org/series/80419/ State : success == Summary == CI Bug Log - changes from CI_DRM_8861_full -> Patchwork_18327_full Summary ---

[Intel-gfx] -next on 32-bit thinkpad x60: blinking screen, intel DRM responsible?

Hi! Next has been unusable for a while, but today I got dmesg. Screen is blinking, machine is very unhappy, and ssh is slow/hangs, but I got this: This is recurring patern, usually machine dies like this within 30 minutes of boot. [ 455.019838] perf: interrupt took too long (2509 > 2500),

Re: [Intel-gfx] [PATCH] drm/i915/kbl: Fix revision ID checks

Hi Matt, Thank you for the patch! Yet something to improve: [auto build test ERROR on drm-intel/for-linux-next] [also build test ERROR on drm-tip/drm-tip next-20200807] [cannot apply to v5.8] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/kbl: Fix revision ID checks

== Series Details == Series: drm/i915/kbl: Fix revision ID checks URL : https://patchwork.freedesktop.org/series/80419/ State : success == Summary == CI Bug Log - changes from CI_DRM_8861 -> Patchwork_18327 Summary --- **SUCCESS**

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/kbl: Fix revision ID checks

== Series Details == Series: drm/i915/kbl: Fix revision ID checks URL : https://patchwork.freedesktop.org/series/80419/ State : warning == Summary == $ dim sparse --fast origin/drm-tip Sparse version: v0.6.0 Fast mode used, each commit won't be checked separately.

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/kbl: Fix revision ID checks

== Series Details == Series: drm/i915/kbl: Fix revision ID checks URL : https://patchwork.freedesktop.org/series/80419/ State : warning == Summary == $ dim checkpatch origin/drm-tip d391445dba5b drm/i915/kbl: Fix revision ID checks -:126: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'dev_priv'

[Intel-gfx] [PATCH] drm/i915/kbl: Fix revision ID checks

We usually assume that increasing PCI device revision ID's translates to newer steppings; macros like IS_KBL_REVID() that we use rely on this behavior. Unfortunately this turns out to not be true on KBL; the newer device 2 revision ID's sometimes go backward to older steppings. The situation is