From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Fixes that failed to apply to v5.3-rc2
Date: Mon, 29 Jul 2019 16:08:25 +0300 [thread overview]
Message-ID: <87r269ng3a.fsf@intel.com> (raw)
The following commits have been marked as Cc: stable or fixing something
in v5.3-rc2 or earlier, but failed to cherry-pick to
drm-intel-fixes. Please see if they are worth backporting, and please do
so if they are.
Failed to cherry-pick:
18398904ca9e ("drm/i915: Only recover active engines")
092be382a260 ("drm/i915: Lift intel_engines_resume() to callers")
fff8102aaed5 ("drm/i915/execlists: Process interrupted context on reset")
6c2b0103ad92 ("drm/i915: Fix and improve MCR selection logic")
Cherry-pick fine but fail to build (*):
2a8db563311a ("drm/i915: Use maximum write flush for pwrite_gtt")
BR,
Jani.
(*)
drivers/gpu/drm/i915/i915_gem.c: In function ‘i915_gem_gtt_pwrite_fast’:
drivers/gpu/drm/i915/i915_gem.c:653:4: error: implicit declaration of function ‘intel_gt_flush_ggtt_writes’; did you mean ‘i915_gem_flush_ggtt_writes’? [-Werror=implicit-function-declaration]
intel_gt_flush_ggtt_writes(ggtt->vm.gt);
^~~~~~~~~~~~~~~~~~~~~~~~~~
i915_gem_flush_ggtt_writes
drivers/gpu/drm/i915/i915_gem.c:653:39: error: ‘struct i915_address_space’ has no member named ‘gt’
intel_gt_flush_ggtt_writes(ggtt->vm.gt);
^
drivers/gpu/drm/i915/i915_gem.c:682:37: error: ‘struct i915_address_space’ has no member named ‘gt’
intel_gt_flush_ggtt_writes(ggtt->vm.gt);
^
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2019-07-29 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 13:08 Jani Nikula [this message]
2019-08-13 8:06 ` Fixes that failed to apply to v5.3-rc2 Jani Nikula
2019-08-13 8:14 ` Chris Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r269ng3a.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox