From: Greg KH <gregkh@linuxfoundation.org>
To: "Deucher, Alexander" <Alexander.Deucher@amd.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"sashal@kernel.org" <sashal@kernel.org>,
"Zuo, Jerry" <Jerry.Zuo@amd.com>,
"Pillai, Aurabindo" <Aurabindo.Pillai@amd.com>,
"Siqueira, Rodrigo" <Rodrigo.Siqueira@amd.com>,
"Wheeler, Daniel" <Daniel.Wheeler@amd.com>
Subject: Re: [PATCH 1/2] drm/amd/display: Skip Invalid Streams from DSC Policy
Date: Sat, 7 Dec 2024 07:29:54 +0100 [thread overview]
Message-ID: <2024120738-colossal-acutely-c465@gregkh> (raw)
In-Reply-To: <BL1PR12MB5144F95DBC0D3EEE437F568BF7312@BL1PR12MB5144.namprd12.prod.outlook.com>
On Fri, Dec 06, 2024 at 04:17:58PM +0000, Deucher, Alexander wrote:
> [Public]
>
> > -----Original Message-----
> > From: Greg KH <gregkh@linuxfoundation.org>
> > Sent: Friday, December 6, 2024 8:13 AM
> > To: Deucher, Alexander <Alexander.Deucher@amd.com>
> > Cc: stable@vger.kernel.org; sashal@kernel.org; Zuo, Jerry
> > <Jerry.Zuo@amd.com>; Pillai, Aurabindo <Aurabindo.Pillai@amd.com>; Siqueira,
> > Rodrigo <Rodrigo.Siqueira@amd.com>; Wheeler, Daniel
> > <Daniel.Wheeler@amd.com>
> > Subject: Re: [PATCH 1/2] drm/amd/display: Skip Invalid Streams from DSC Policy
> >
> > On Tue, Dec 03, 2024 at 08:11:14AM +0100, Greg KH wrote:
> > > On Mon, Dec 02, 2024 at 12:28:32PM -0500, Alex Deucher wrote:
> > > > From: Fangzhi Zuo <Jerry.Zuo@amd.com>
> > > >
> > > > Streams with invalid new connector state should be elimiated from
> > > > dsc policy.
> > > >
> > > > Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3405
> > > > Reviewed-by: Aurabindo Pillai <aurabindo.pillai@amd.com>
> > > > Signed-off-by: Fangzhi Zuo <Jerry.Zuo@amd.com>
> > > > Signed-off-by: Rodrigo Siqueira <rodrigo.siqueira@amd.com>
> > > > Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
> > > > Signed-off-by: Alex Deucher <alexander.deucher@amd.com> (cherry
> > > > picked from commit 9afeda04964281e9f708b92c2a9c4f8a1387b46e)
> > > > Cc: stable@vger.kernel.org
> > > > ---
> > > > .../drm/amd/display/amdgpu_dm/amdgpu_dm_mst_types.c | 13
> > > > ++++++++++++-
> > > > 1 file changed, 12 insertions(+), 1 deletion(-)
> > >
> > > What kernel tree(s) is this series for?
> >
> > Dropping from my queue due to lack of response :(
> >
> > Please resend if you need this, with a hint of what we are supposed to be applying it
> > to.
>
> Sorry I just saw this now. This landed in 6.13, but it was determined that it needed to go to stable. Ideally at least 6.11 and 6.12.
But it's already in 6.11.11 and 6.12.2 so I guess all is ok :)
next prev parent reply other threads:[~2024-12-07 6:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 17:28 [PATCH 1/2] drm/amd/display: Skip Invalid Streams from DSC Policy Alex Deucher
2024-12-02 17:28 ` [PATCH 2/2] drm/amd/display: Fix incorrect DSC recompute trigger Alex Deucher
2024-12-02 19:15 ` [PATCH 1/2] drm/amd/display: Skip Invalid Streams from DSC Policy Sasha Levin
2024-12-03 18:13 ` Sasha Levin
2024-12-03 7:11 ` Greg KH
2024-12-06 13:12 ` Greg KH
2024-12-06 16:17 ` Deucher, Alexander
2024-12-07 6:29 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-06 16:21 Alex Deucher
2024-12-06 23:11 ` 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=2024120738-colossal-acutely-c465@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Alexander.Deucher@amd.com \
--cc=Aurabindo.Pillai@amd.com \
--cc=Daniel.Wheeler@amd.com \
--cc=Jerry.Zuo@amd.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=sashal@kernel.org \
--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