From: Greg KH <gregkh@linuxfoundation.org>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: mikhail.v.gavrilov@gmail.com,
Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
amd-gfx@lists.freedesktop.org,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] drm/amd/display: fix corruption with high refresh rates on DCN 3.0
Date: Mon, 29 Jul 2024 11:45:43 +0200 [thread overview]
Message-ID: <2024072937-undivided-liver-b59b@gregkh> (raw)
In-Reply-To: <a3af3f0b-df81-4407-a38d-2fa35b33b08c@leemhuis.info>
On Mon, Jul 29, 2024 at 10:31:38AM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 16.07.24 19:33, Alex Deucher wrote:
> > This reverts commit bc87d666c05a13e6d4ae1ddce41fc43d2567b9a2 and the
> > register changes from commit 6d4279cb99ac4f51d10409501d29969f687ac8dc.
> >
> > Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3478
> > Cc: mikhail.v.gavrilov@gmail.com
> > Cc: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
> > Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> > [...]
>
> Hi Greg, quick note, as I don't see the quoted patch in your 6.10-queue
> yet: you might want to pick up e3615bd198289f ("drm/amd/display: fix
> corruption with high refresh rates on DCN 3.0") [v6.11-rc1, contains
> table tag] rather sooner than later for 6.10.y, as the problem
> apparently hit a few people and even made the news:
> https://lore.kernel.org/all/20240723042420.GA1455@sol.localdomain/
> https://www.reddit.com/r/archlinux/comments/1eaxjzo/linux_610_causes_screen_flicker_on_amd_gpus/
Thanks, now queued up.
greg k-h
prev parent reply other threads:[~2024-07-29 9:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240716173322.4061791-1-alexander.deucher@amd.com>
2024-07-29 8:31 ` [PATCH] drm/amd/display: fix corruption with high refresh rates on DCN 3.0 Linux regression tracking (Thorsten Leemhuis)
2024-07-29 9:45 ` Greg KH [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=2024072937-undivided-liver-b59b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Rodrigo.Siqueira@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox