From: Leo Li <sunpeng.li@amd.com>
To: Alex Deucher <alexander.deucher@amd.com>, amd-gfx@lists.freedesktop.org
Cc: Charlene Liu <Charlene.Liu@amd.com>,
Prike Liang <Prike.Liang@amd.com>,
Hansen Dsouza <Hansen.Dsouza@amd.com>
Subject: Re: [PATCH 5/6] drm/amd/display: Add DCN316 resource and SMU clock manager
Date: Wed, 16 Feb 2022 10:55:36 -0500 [thread overview]
Message-ID: <300736b3-eff0-487e-e149-8a3feefcb89d@amd.com> (raw)
In-Reply-To: <20220215214447.2234978-4-alexander.deucher@amd.com>
On 2022-02-15 16:44, Alex Deucher wrote:
> diff --git a/drivers/gpu/drm/amd/display/dc/gpio/Makefile b/drivers/gpu/drm/amd/display/dc/gpio/Makefile
> index c5ddade8b187..a1bf2128feba 100644
> --- a/drivers/gpu/drm/amd/display/dc/gpio/Makefile
> +++ b/drivers/gpu/drm/amd/display/dc/gpio/Makefile
> @@ -106,6 +106,7 @@ GPIO_DCN30 = hw_translate_dcn30.o hw_factory_dcn30.o
> AMD_DAL_GPIO_DCN30 = $(addprefix $(AMDDALPATH)/dc/gpio/dcn30/,$(GPIO_DCN30))
>
> AMD_DISPLAY_FILES += $(AMD_DAL_GPIO_DCN30)
> +
Looks like we can drop this newline. Otherwise,
Reviewed-by: Leo Li <sunpeng.li@amd.com>
> endif
> ###############################################################################
> # Diagnostics on FPGA
> -- 2.34.1
next prev parent reply other threads:[~2022-02-16 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 21:44 [PATCH 0/6] Update DCN 3.1 support for 3.1.6 Alex Deucher
2022-02-15 21:44 ` [PATCH 3/6] drm/amd/display: configure dc hw resource for DCN 3.1.6 Alex Deucher
2022-02-16 15:25 ` Leo Li
2022-02-15 21:44 ` [PATCH 4/6] drm/amd/display: Add DMUB support for DCN316 Alex Deucher
2022-02-16 19:46 ` Harry Wentland
2022-02-15 21:44 ` [PATCH 5/6] drm/amd/display: Add DCN316 resource and SMU clock manager Alex Deucher
2022-02-16 15:55 ` Leo Li [this message]
2022-02-15 21:44 ` [PATCH 6/6] drm/amdgpu/discovery: Add sw DM function for 3.1.6 DCE Alex Deucher
2022-02-16 15:57 ` Leo Li
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=300736b3-eff0-487e-e149-8a3feefcb89d@amd.com \
--to=sunpeng.li@amd.com \
--cc=Charlene.Liu@amd.com \
--cc=Hansen.Dsouza@amd.com \
--cc=Prike.Liang@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.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