From: Jani Nikula <jani.nikula@intel.com>
To: "Matt Roper" <matthew.d.roper@intel.com>,
"José Roberto de Souza" <jose.souza@intel.com>,
"Chris Wilson" <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] Fixes that failed to apply to v5.6-rc3
Date: Mon, 02 Mar 2020 11:30:16 +0200 [thread overview]
Message-ID: <874kv7qf2v.fsf@intel.com> (raw)
In-Reply-To: <877e08shcs.fsf@intel.com>
On Thu, 27 Feb 2020, Jani Nikula <jani.nikula@intel.com> wrote:
> Hi all -
>
> The following commits have been marked as Cc: stable or fixing something
> in v5.6-rc3 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:
> 837b63e60878 ("drm/i915: Program MBUS with rmw during initialization")
> 87e04f75928b ("drm/i915/tgl: Add Wa_22010178259:tgl")
> df1a5bfc16f3 ("drm/i915/psr: Force PSR probe only after full initialization")
Thanks for the backports of these, pushed to drm-intel-fixes.
BR,
Jani.
>
> This one was fine to cherry-pick, but caused problematic (for me!)
> conflicts in drm-tip rebuild:
> 42fb60de3129 ("drm/i915/gem: Don't leak non-persistent requests on changing engines")
>
> BR,
> Jani.
--
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 prev parent reply other threads:[~2020-03-02 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 5:56 [Intel-gfx] Fixes that failed to apply to v5.6-rc3 Jani Nikula
2020-02-27 20:55 ` [Intel-gfx] [PATCH backported to v5.6-rc3] drm/i915/psr: Force PSR probe only after full initialization José Roberto de Souza
2020-02-28 2:02 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915/psr: Force PSR probe only after full initialization (rev8) Patchwork
2020-03-02 9:30 ` Jani Nikula [this message]
2020-03-16 13:14 ` [Intel-gfx] Fixes that failed to apply to v5.6-rc3 Jani Nikula
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=874kv7qf2v.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jose.souza@intel.com \
--cc=matthew.d.roper@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.