From: Greg KH <gregkh@linuxfoundation.org>
To: Jonathan Gray <jsg@jsg.id.au>
Cc: dri-devel@lists.freedesktop.org, stable@vger.kernel.org
Subject: Re: [PATCH 6.6.y] Revert "drm/amd/display: Skip Recompute DSC Params if no Stream on Link"
Date: Tue, 8 Oct 2024 11:22:56 +0200 [thread overview]
Message-ID: <2024100842-tidiness-buzz-ad6a@gregkh> (raw)
In-Reply-To: <20241007035711.46624-1-jsg@jsg.id.au>
On Mon, Oct 07, 2024 at 02:57:11PM +1100, Jonathan Gray wrote:
> This reverts commit a53841b074cc196c3caaa37e1f15d6bc90943b97.
>
> duplicated a change made in 6.6.46
> 718d83f66fb07b2cab89a1fc984613a00e3db18f
>
> Cc: stable@vger.kernel.org # 6.6
> Signed-off-by: Jonathan Gray <jsg@jsg.id.au>
> ---
> drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_mst_types.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_mst_types.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_mst_types.c
> index 7fb11445a28f..d390e3d62e56 100644
> --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_mst_types.c
> +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_mst_types.c
> @@ -1266,9 +1266,6 @@ static bool is_dsc_need_re_compute(
> }
> }
>
> - if (new_stream_on_link_num == 0)
> - return false;
> -
> if (new_stream_on_link_num == 0)
> return false;
>
> --
> 2.46.1
>
The whole drm tree is messed up when it comes to stable patches.
Duplicates like this happen all the time due to their bizarre workflow
that causes this to happen at least once a release, and is still a major
pain to deal with.
I dread the -rc1 merge window each time for the drm patches and put them
off until I have gotten through everything else. Can you please work
with those developers to make this go better to prevent this from
constantly happening?
thanks,
greg k-h
prev parent reply other threads:[~2024-10-08 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 3:57 [PATCH 6.6.y] Revert "drm/amd/display: Skip Recompute DSC Params if no Stream on Link" Jonathan Gray
2024-10-08 9:22 ` 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=2024100842-tidiness-buzz-ad6a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsg@jsg.id.au \
--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;
as well as URLs for NNTP newsgroup(s).