Chris Wilson 721017cf4b drm/i915/gem: Ignore readonly failures when updating relocs ... If the user passes in a readonly reloc[], by the time we notice we have already committed to modifying the execobjects, or have indeed done so already. Reporting the failure just compounds the issue as we have no second pass to fall back to anymore. "Be damned if you do, and damned if you don't." Testcase: igt/gem_exec_reloc/readonly Fixes: 7dc8f11437 ("drm/i915/gem: Drop relocation slowpath") References: fddcd00a49 ("drm/i915: Force the slow path after a user-write error") Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Matthew Auld <matthew.auld@intel.com> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> Reviewed-by: Andi Shyti <andi.shyti@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20200331162150.3635-1-chris@chris-wilson.co.uk (cherry picked from commit 97a37c919f) Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>		2020-04-06 10:31:23 -07:00
..
drm	drm/i915/gem: Ignore readonly failures when updating relocs	2020-04-06 10:31:23 -07:00
host1x	drm/tegra: Fixes for v5.6-rc1	2020-02-07 12:22:30 +10:00
ipu-v3
vga	vga: Fix Kconfig indentation	2019-11-20 17:40:32 +01:00
Makefile