Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Leo Li <sunpeng.li@amd.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Sasha Levin <sashal@kernel.org>, <stable@vger.kernel.org>,
	<amd-gfx@lists.freedesktop.org>,
	David Weber <weber.aulendorf@gmail.com>,
	"Mario Limonciello (AMD)" <superm1@kernel.org>,
	Alex Deucher <alexander.deucher@amd.com>
Subject: Re: [PATCH 7.1.y] drm/amd/display: Exit idle optimizations before programming
Date: Fri, 7 Aug 2026 09:36:04 -0400	[thread overview]
Message-ID: <e1b3c2ec-315d-4e44-9079-3253ad4c2f5b@amd.com> (raw)
In-Reply-To: <2026080707-deem-ascend-927c@gregkh>



On 2026-08-07 05:20, Greg KH wrote:
> On Thu, Aug 06, 2026 at 09:42:42AM -0400, Leo Li wrote:
>>
>>
>> On 2026-08-06 07:36, Sasha Levin wrote:
>>> This doesn't apply cleanly to 7.1?
>>>
>>
>> Hi Sasha,
>>
>> Looks like the tagged "Fixes:" hasn't landed in 7.1 yet. This patch depends on it.
>> See the 7.1 backport of it here: https://lore.kernel.org/stable/3956c589-2fbb-49af-b0bb-8aeff0cd56db@amd.com/
> 
> So what are we supposed to do here?

Hi Greg,

The two remaining fixes for 7.1 and 6.18 are this patch, and

[PATCH 7.1.y] drm/amd/display: check GRPH_FLIP status before sending event
    https://lore.kernel.org/stable/20260729173742.950965-2-sunpeng.li@amd.com/

[PATCH 6.18.y] drm/amd/display: check GRPH_FLIP status before sending event
    https://lore.kernel.org/stable/20260729175748.981393-1-sunpeng.li@amd.com/

Looks like Sasha queued them just now:
https://lore.kernel.org/stable/20260806234000.stable-0001@kernel.org/

Thanks, and sorry for the confusion!
Leo


  reply	other threads:[~2026-08-07 13:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05 12:11 FAILED: patch "[PATCH] drm/amd/display: Exit idle optimizations before programming" failed to apply to 7.1-stable tree gregkh
2026-08-05 16:33 ` [PATCH 7.1.y] drm/amd/display: Exit idle optimizations before programming sunpeng.li
2026-08-06 11:36   ` Sasha Levin
2026-08-06 13:42     ` Leo Li
2026-08-07  9:20       ` Greg KH
2026-08-07 13:36         ` Leo Li [this message]
2026-08-07 11:45   ` Sasha Levin

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=e1b3c2ec-315d-4e44-9079-3253ad4c2f5b@amd.com \
    --to=sunpeng.li@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=superm1@kernel.org \
    --cc=weber.aulendorf@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox