From: Greg KH <greg@kroah.com>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 6.5.y 0/2] Fixup for drm/amd/display: apply edge-case DISPCLK WDIVIDER changes to master OTG pipes only
Date: Thu, 12 Oct 2023 19:08:05 +0200 [thread overview]
Message-ID: <2023101256-rare-unshipped-b594@gregkh> (raw)
In-Reply-To: <20231009182037.124395-1-mario.limonciello@amd.com>
On Mon, Oct 09, 2023 at 01:20:35PM -0500, Mario Limonciello wrote:
> commit b206011bf050 ("drm/amd/display: apply edge-case DISPCLK WDIVIDER
> changes to master OTG pipes only") was tagged to stable but fails to
> apply to 6.5.y because resource_is_pipe_type() isn't in 6.5.y.
>
> The commit that adds it is way too big to be stable, but the new symbol
> from that commit is viable. Backport just the new symbol and enum to fix
> the backport.
>
> Mario Limonciello (1):
> drm/amd/display: implement pipe type definition and adding accessors
>
> Samson Tam (1):
> drm/amd/display: apply edge-case DISPCLK WDIVIDER changes to master
> OTG pipes only
>
> .../display/dc/clk_mgr/dcn20/dcn20_clk_mgr.c | 4 +-
> .../display/dc/clk_mgr/dcn32/dcn32_clk_mgr.c | 4 +-
> .../gpu/drm/amd/display/dc/core/dc_resource.c | 35 ++++++
> drivers/gpu/drm/amd/display/dc/inc/resource.h | 106 ++++++++++++++++++
> 4 files changed, 145 insertions(+), 4 deletions(-)
>
> --
> 2.34.1
>
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2023-10-12 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 18:20 [PATCH 6.5.y 0/2] Fixup for drm/amd/display: apply edge-case DISPCLK WDIVIDER changes to master OTG pipes only Mario Limonciello
2023-10-09 18:20 ` [PATCH 6.5.y 1/2] drm/amd/display: implement pipe type definition and adding accessors Mario Limonciello
2023-10-09 18:20 ` [PATCH 6.5.y 2/2] drm/amd/display: apply edge-case DISPCLK WDIVIDER changes to master OTG pipes only Mario Limonciello
2023-10-12 17:08 ` 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=2023101256-rare-unshipped-b594@gregkh \
--to=greg@kroah.com \
--cc=mario.limonciello@amd.com \
--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