From: Greg KH <gregkh@linuxfoundation.org>
To: Mario Limonciello <superm1@kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: Fix regression from "drm/amd/display: Fix MST BW calculation Regression"
Date: Tue, 1 Oct 2024 09:31:42 +0200 [thread overview]
Message-ID: <2024100129-wolf-turbojet-2af1@gregkh> (raw)
In-Reply-To: <652c0f61-450c-415f-9520-68cc596fabb0@kernel.org>
On Fri, Sep 27, 2024 at 09:14:40AM -0500, Mario Limonciello wrote:
> On 9/27/2024 02:41, Greg KH wrote:
> > On Mon, Sep 23, 2024 at 11:23:57PM -0500, Mario Limonciello wrote:
> > > Hello,
> > >
> > > The commit 338567d17627 ("drm/amd/display: Fix MST BW calculation
> > > Regression") caused a regression with some MST displays due to a mistake.
> > >
> > > For 6.11.y here is the series of commits that fixes it:
> > >
> > > commit 4599aef0c97b ("drm/amd/display: Fix Synaptics Cascaded Panamera DSC
> > > Determination")
> >
> > I don't see this commit in Linus's tree :(
>
> Gah; sorry I have a lot of remotes and didn't realize which one I was on
> when regressing this. Here's the right hashes.
>
> 4437936c6b69 ("drm/amd/display: Fix Synaptics Cascaded Panamera DSC
> Determination")
>
> >
> > > commit ecc4038ec1de ("drm/amd/display: Add DSC Debug Log")
> > > commit b2b4afb9cf07 ("drm/amdgpu/display: Fix a mistake in revert commit")
> >
> > Nor either of these :(
>
> commit 3715112c1b35 ("drm/amd/display: Add DSC Debug Log")
> commit 7745a1dee0a6 ("drm/amdgpu/display: Fix a mistake in revert commit")
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2024-10-01 7:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 4:23 Fix regression from "drm/amd/display: Fix MST BW calculation Regression" Mario Limonciello
2024-09-27 7:41 ` Greg KH
2024-09-27 14:14 ` Mario Limonciello
2024-10-01 7:31 ` 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=2024100129-wolf-turbojet-2af1@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=superm1@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