There are still many places where we can inject failures, but doing so without preparation may make CI unhappy as it will treat any new ERROR/WARN very seriously. Mitigate that by converting some of dmesg messages to debug after injecting fake error. Michal Wajdeczko (4): drm/i915: Report -ENODEV after injecting probe failure drm/i915: Add i915 to i915_inject_probe_failure drm/i915/uc: Inject load errors into intel_uc_init_hw drm/i915/wopcm: Don't fail on WOPCM partitioning failure .../gpu/drm/i915/display/intel_connector.c | 2 +- drivers/gpu/drm/i915/gt/intel_engine_cs.c | 2 +- drivers/gpu/drm/i915/gt/uc/intel_uc.c | 11 +++ drivers/gpu/drm/i915/i915_drv.c | 27 ++++---- drivers/gpu/drm/i915/i915_drv.h | 19 ++++-- drivers/gpu/drm/i915/i915_gem.c | 24 ++----- drivers/gpu/drm/i915/i915_pci.c | 4 +- drivers/gpu/drm/i915/intel_gvt.c | 2 +- drivers/gpu/drm/i915/intel_uncore.c | 2 +- drivers/gpu/drm/i915/intel_wopcm.c | 68 ++++++++++--------- drivers/gpu/drm/i915/intel_wopcm.h | 11 ++- 11 files changed, 97 insertions(+), 75 deletions(-) -- 2.19.2 _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
