From: Greg KH <gregkh@linuxfoundation.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: "Sasha Levin" <sashal@kernel.org>,
"Linux kernel regressions list" <regressions@lists.linux.dev>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Dave Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: Some 7.1-post fixes that might be worth picking up rather sooner than later
Date: Tue, 7 Jul 2026 16:32:21 +0200 [thread overview]
Message-ID: <2026070708-hurricane-tackle-43e1@gregkh> (raw)
In-Reply-To: <2026070707-brigade-petted-5ef2@gregkh>
On Tue, Jul 07, 2026 at 01:48:29PM +0200, Greg KH wrote:
> On Tue, Jul 07, 2026 at 12:19:20PM +0200, Thorsten Leemhuis wrote:
> > [CCing a few people]
> >
> > On 6/22/26 07:32, Greg KH wrote:
> > > On Fri, Jun 19, 2026 at 11:43:41AM +0200, Greg KH wrote:
> > >> On Fri, Jun 19, 2026 at 08:04:35AM +0200, Thorsten Leemhuis wrote:
> > >>> Hi Stable Team! From the regressions point I think it might be nice to
> > >>> pick up the following changes for the next round of stable updates (e.g.
> > >>> 7.1.2), as they seem to fix regressions I've seen multiple people report
> > >>> with 7.1:
> > >>> [...]
> > >>> * 12f58a6caad3be ("drm/amd/display: Fix Color Manager (3DLUT, Shaper,
> > >>> Blend)") [v7.1-post]
> > >
> > > This doesn't apply to 7.1.y, and would need a working backport.
> > Just a quick status update twimc:
> >
> > I pointed that out in
> > https://gitlab.freedesktop.org/drm/amd/-/work_items/5396 , but nothing
> > happened from the AMD side afaics. They have much on their plate, I
> > fully understand that, I guess it fell through the cracks (maybe this
> > mail helps). Thing is: the backport of the revert is quite big, so
> > nobody else (including me) did yet dare to submit it themselves.
> >
> > So two weeks later the regression caused by e56e3cff2a1bb2
> > ("drm/amd/display: Sync dcn42 with DC 3.2.373") [v7.1-rc1] is still
> > unfixed in 7.1.y as far as I can see it -- a regression that is known
> > since more than two months now, as the revert to fix it (12f58a6caad3be,
> > mentioned in the quote above) was submitted already on 2026-04-29, but
> > only made it to mainline during the merge window for 7.2 (this is
> > another thing that afaics fell through the cracks; sadly I only became
> > aware of the regression after 7.1 was out, otherwise I would have made
> > noise earlier to get it included in 7.1).
>
> So should 12f58a6caad3be be added to the stable queues?
It doesn't apply cleanly, so I'd need a backported version.
thanks,
greg k-h
next prev parent reply other threads:[~2026-07-07 14:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 6:04 Some 7.1-post fixes that might be worth picking up rather sooner than later Thorsten Leemhuis
2026-06-19 9:43 ` Greg KH
2026-06-22 5:32 ` Greg KH
2026-07-07 10:19 ` Thorsten Leemhuis
2026-07-07 11:48 ` Greg KH
2026-07-07 14:32 ` Greg KH [this message]
2026-07-07 15:19 ` Deucher, Alexander
2026-07-07 15:28 ` Thorsten Leemhuis
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=2026070708-hurricane-tackle-43e1@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.