From: Aurabindo Pillai <aurabindo.pillai@amd•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Alex Deucher <alexdeucher@gmail•com>
Cc: Wesley Chalmers <Wesley.Chalmers@amd•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the amdgpu tree
Date: Mon, 10 Jul 2023 09:21:44 -0400 [thread overview]
Message-ID: <54adffa8-b500-e1b4-7274-9a5354be8cfe@amd.com> (raw)
In-Reply-To: <20230710082534.762599c8@canb.auug.org.au>
On 7/9/2023 6:25 PM, Stephen Rothwell wrote:
> Hi all,
>
> Commit
>
> aeddb7d13ad3 ("drm/amd/display: Block optimize on consecutive FAMS enables")
>
> is missing a Signed-off-by from its author.
>
Hi Stephen,
Not sure how the tags went missing, but here is the full commit
(a7d8d8bcbd9af8d4aa1580bffd418af78384040f) information from
amd-staging-drm-next:
drm/amd/display: Block optimize on consecutive FAMS enables
[WHY]
It is possible to commit state multiple times in rapid succession with
FAMS enabled; if each of these commits were to set optimized_required,
then the user may see latency.
[HOW]
fw_based_mclk_switching is currently not used in dc->clk_mgr; use it
to track whether the current state has FAMS enabled;
if it has, then do not disable FAMS in prepare_bandwidth, and do
not set
optimized_required.
Reviewed-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd•com>
Signed-off-by: Wesley Chalmers <Wesley.Chalmers@amd•com>
Tested-by: Daniel Wheeler <daniel.wheeler@amd•com>
Signed-off-by: Alex Deucher <alexander.deucher@amd•com>
Acked-by: Hamza Mahfooz <hamza.mahfooz@amd•com>
--
Thanks & Regards,
Aurabindo Pillai
next prev parent reply other threads:[~2023-07-10 13:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-09 22:25 linux-next: Signed-off-by missing for commit in the amdgpu tree Stephen Rothwell
2023-07-10 13:21 ` Aurabindo Pillai [this message]
2023-07-10 13:24 ` Alex Deucher
-- strict thread matches above, loose matches on Subject: below --
2025-04-21 23:36 Stephen Rothwell
2025-04-07 21:55 Stephen Rothwell
2023-01-09 21:58 Stephen Rothwell
2023-01-09 22:04 ` Alex Deucher
2022-07-13 22:22 Stephen Rothwell
2022-06-01 21:57 Stephen Rothwell
2022-05-14 10:11 Stephen Rothwell
2022-01-11 21:23 Stephen Rothwell
2022-01-03 23:50 Stephen Rothwell
2021-03-28 21:24 Stephen Rothwell
2021-03-29 14:17 ` Mark Yacoub
2021-03-29 15:34 ` Alex Deucher
2021-03-29 15:35 ` Mark Yacoub
2021-03-21 21:17 Stephen Rothwell
2020-11-01 21:28 Stephen Rothwell
2020-09-15 22:27 Stephen Rothwell
2020-01-27 21:38 Stephen Rothwell
2019-07-16 19:37 Stephen Rothwell
2019-07-03 21:43 Stephen Rothwell
2019-06-22 13:54 Stephen Rothwell
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=54adffa8-b500-e1b4-7274-9a5354be8cfe@amd.com \
--to=aurabindo.pillai@amd$(echo .)com \
--cc=Wesley.Chalmers@amd$(echo .)com \
--cc=alexdeucher@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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