From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Timur Kristóf" <timur.kristof@gmail.com>
Cc: "Rosen Penev" <rosenp@gmail.com>,
"Christian König" <christian.koenig@amd.com>,
"Harry Wentland" <harry.wentland@amd.com>,
"Leo Li" <sunpeng.li@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Kenneth Feng" <kenneth.feng@amd.com>,
"Alex Hung" <alex.hung@amd.com>,
"Lijo Lazar" <lijo.lazar@amd.com>, "chr[]" <chris@rudorff.com>,
"Sasha Levin" <sashal@kernel.org>,
"Wentao Liang" <vulab@iscas.ac.cn>,
"open list:AMD DISPLAY CORE" <amd-gfx@lists.freedesktop.org>,
"open list:DRM DRIVERS" <dri-devel@lists.freedesktop.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv2 for 6.112 and 6.6 0/2] amdgpu: fix panic on old GPUs
Date: Thu, 19 Mar 2026 12:53:47 +0100 [thread overview]
Message-ID: <2026031940-single-buddy-d53d@gregkh> (raw)
In-Reply-To: <2332143.t9SDvczpPo@timur-hyperion>
On Sun, Mar 08, 2026 at 02:15:54PM +0100, Timur Kristóf wrote:
> On Wednesday, March 4, 2026 11:23:33 PM Central European Standard Time Rosen
> Penev wrote:
> > The DC code path just works bettter. So what if suspend is broken. I
> > would much rather a working system. Hyprsunset for example doesn't
> > work without DC. No idea why.
>
> It's great that it works better for you. Unfortunately that isn't the case for
> everyone. It wasn't feature complete until 6.19 so it wasn't a feasible
> default until then on these GPUs. Since 6.19 I would say it's pretty good now.
>
> > Speaking of suspend, the fixes for it are fairly trivial to backport
> > to 6.12 as well.
>
> Yes. I don't understand why those patches weren't backported.
> Like I said, I sent them for backporting to 6.17 many months ago and expected
> to see them backported to older kernels as well.
>
> > > Now that the situation is cleared up, is there anything else we need to do
> > > for these two patches here?
> >
> > Speaking of which, it's probably best to take over here. It's not fun
> > dealing with stable. I also didn't author these patches.
>
> The question was meant for Christian and Greg.
> What do I need to do to get these patches backported?
I've taken them now, thanks.
greg k-h
prev parent reply other threads:[~2026-03-19 11:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-28 4:53 [PATCHv2 for 6.112 and 6.6 0/2] amdgpu: fix panic on old GPUs Rosen Penev
2026-02-28 4:53 ` [PATCHv2 for 6.112 and 6.6 1/2] drm/amd/display: Add pixel_clock to amd_pp_display_configuration Rosen Penev
2026-02-28 4:53 ` [PATCHv2 for 6.112 and 6.6 2/2] drm/amd/pm: Use pm_display_cfg in legacy DPM (v2) Rosen Penev
2026-03-04 4:03 ` [PATCHv2 for 6.112 and 6.6 0/2] amdgpu: fix panic on old GPUs Rosen Penev
2026-03-04 8:10 ` Christian König
2026-03-04 9:09 ` Timur Kristóf
2026-03-04 10:06 ` Christian König
2026-03-04 12:44 ` Timur Kristóf
2026-03-04 22:23 ` Rosen Penev
2026-03-08 13:15 ` Timur Kristóf
2026-03-19 11:53 ` Greg Kroah-Hartman [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=2026031940-single-buddy-d53d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=airlied@gmail.com \
--cc=alex.hung@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=chris@rudorff.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=kenneth.feng@amd.com \
--cc=lijo.lazar@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rosenp@gmail.com \
--cc=sashal@kernel.org \
--cc=simona@ffwll.ch \
--cc=sunpeng.li@amd.com \
--cc=timur.kristof@gmail.com \
--cc=vulab@iscas.ac.cn \
/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