From: Jani Nikula <jani.nikula@intel.com>
To: "Hogander, Jouni" <jouni.hogander@intel.com>,
"Manna, Animesh" <animesh.manna@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: Fixes that failed to pick to v6.10-rc2
Date: Wed, 19 Jun 2024 11:56:42 +0300 [thread overview]
Message-ID: <87o77xfgz9.fsf@intel.com> (raw)
In-Reply-To: <44f0ef6246174c1faca726a86901cd31c9eb5ab0.camel@intel.com>
On Wed, 05 Jun 2024, "Hogander, Jouni" <jouni.hogander@intel.com> wrote:
> On Wed, 2024-06-05 at 13:06 +0300, Jani Nikula wrote:
>>
>> Jouni, Animesh, there are some PSR commits with Fixes: pointing at
>> commits in v6.9 or v6.10-rc1.
>>
>> This does not apply cleanly to -rc1:
>> d07a578703db ("drm/i915/display: Do not print "psr: enabled" for on
>> Panel Replay")
>>
>> This applies but does not build:
>> 45b5853114ad ("drm/i915/psr: Get Early Transport status in
>> intel_psr_pipe_get_config")
>>
>> This applies and builds but decided to punt because of the above:
>> cd43a85ec3c6 ("drm/i915/psr: Use enable boolean from intel_crtc_state
>> for Early Transport")
>>
>> If these are important fixes to be backported to v6.10, please
>> provide
>> the backports.
>
> First patch is just for shaping debugfs interface printout. I think
> that is ok to leave out.
>
> Early transport is disabled by default currently -> should be ok to
> leave out two last patches.
There have been more PSR patches in drm-intel-next with Fixes: pointing
at commits upstream. I've skipped them too. But it should be noted that
once drm-intel-next gets merged upstream for v6.11, the stable team will
inevitably start picking those commits up.
BR,
Jani.
>
> BR,
>
> Jouni Högander
>>
>> BR,
>> Jani.
>>
>>
>
--
Jani Nikula, Intel
prev parent reply other threads:[~2024-06-19 8:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 10:06 Fixes that failed to pick to v6.10-rc2 Jani Nikula
2024-06-05 10:13 ` Hogander, Jouni
2024-06-19 8:56 ` Jani Nikula [this message]
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=87o77xfgz9.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=animesh.manna@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jouni.hogander@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.