From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: stylon.wang@amd.com, Nicholas.Kazlauskas@amd.com,
Rodrigo.Siqueira@amd.com, alexander.deucher@amd.com,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] drm/amd/display: Fix ineffective setting of max bpc property" failed to apply to 5.7-stable tree
Date: Thu, 2 Jul 2020 13:59:05 -0400 [thread overview]
Message-ID: <20200702175905.GE2722994@sasha-vm> (raw)
In-Reply-To: <159343042310143@kroah.com>
On Mon, Jun 29, 2020 at 01:33:43PM +0200, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 5.7-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From fa7041d9d2fc7401cece43f305eb5b87b7017fc4 Mon Sep 17 00:00:00 2001
>From: Stylon Wang <stylon.wang@amd.com>
>Date: Fri, 12 Jun 2020 19:04:18 +0800
>Subject: [PATCH] drm/amd/display: Fix ineffective setting of max bpc property
>
>[Why]
>Regression was introduced where setting max bpc property has no effect
>on the atomic check and final commit. It has the same effect as max bpc
>being stuck at 8.
>
>[How]
>Correctly propagate max bpc with the new connector state.
>
>Signed-off-by: Stylon Wang <stylon.wang@amd.com>
>Reviewed-by: Nicholas Kazlauskas <Nicholas.Kazlauskas@amd.com>
>Acked-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
>Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
>Cc: stable@vger.kernel.org
I've grabbed this patch as a dependency and queued both for 5.7:
cbd14ae7ea93 ("drm/amd/display: Fix incorrectly pruned modes with deep
color").
--
Thanks,
Sasha
prev parent reply other threads:[~2020-07-02 17:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 11:33 FAILED: patch "[PATCH] drm/amd/display: Fix ineffective setting of max bpc property" failed to apply to 5.7-stable tree gregkh
2020-07-02 17:59 ` Sasha Levin [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=20200702175905.GE2722994@sasha-vm \
--to=sashal@kernel.org \
--cc=Nicholas.Kazlauskas@amd.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=alexander.deucher@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=stylon.wang@amd.com \
/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