From: Hamza Mahfooz <hamza.mahfooz@amd.com>
To: Nathan Chancellor <nathan@kernel.org>,
harry.wentland@amd.com, sunpeng.li@amd.com,
Rodrigo.Siqueira@amd.com, alexander.deucher@amd.com,
christian.koenig@amd.com, Xinhui.Pan@amd.com
Cc: dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
patches@lists.linux.dev
Subject: Re: [PATCH] drm/amd/display: Respect CONFIG_FRAME_WARN=0 in DML2
Date: Wed, 18 Oct 2023 15:06:29 -0400 [thread overview]
Message-ID: <263305cf-bedd-4419-a136-cecffd0eac89@amd.com> (raw)
In-Reply-To: <20231018-amdgpu-dml2-respect-frame_warn-v1-1-43ec8d153743@kernel.org>
On 10/18/23 14:45, Nathan Chancellor wrote:
> display_mode_code.c is unconditionally built with
> -Wframe-larger-than=2048, which causes warnings even when
> CONFIG_FRAME_WARN has been set to 0, which should show no warnings.
>
> Use the existing $(frame_warn_flag) variable, which handles this
> situation. This is basically commit 25f178bbd078 ("drm/amd/display:
> Respect CONFIG_FRAME_WARN=0 in dml Makefile") but for DML2.
>
> Fixes: 7966f319c66d ("drm/amd/display: Introduce DML2")
> Signed-off-by: Nathan Chancellor <nathan@kernel.org>
Applied, thanks!
> ---
> drivers/gpu/drm/amd/display/dc/dml2/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/display/dc/dml2/Makefile b/drivers/gpu/drm/amd/display/dc/dml2/Makefile
> index f35ed8de260d..66431525f2a0 100644
> --- a/drivers/gpu/drm/amd/display/dc/dml2/Makefile
> +++ b/drivers/gpu/drm/amd/display/dc/dml2/Makefile
> @@ -61,7 +61,7 @@ ifneq ($(CONFIG_FRAME_WARN),0)
> frame_warn_flag := -Wframe-larger-than=2048
> endif
>
> -CFLAGS_$(AMDDALPATH)/dc/dml2/display_mode_core.o := $(dml2_ccflags) -Wframe-larger-than=2048
> +CFLAGS_$(AMDDALPATH)/dc/dml2/display_mode_core.o := $(dml2_ccflags) $(frame_warn_flag)
> CFLAGS_$(AMDDALPATH)/dc/dml2/display_mode_util.o := $(dml2_ccflags)
> CFLAGS_$(AMDDALPATH)/dc/dml2/dml2_wrapper.o := $(dml2_ccflags)
> CFLAGS_$(AMDDALPATH)/dc/dml2/dml2_utils.o := $(dml2_ccflags)
>
> ---
> base-commit: cd90511557fdfb394bb4ac4c3b539b007383914c
> change-id: 20231018-amdgpu-dml2-respect-frame_warn-536e19b69ce0
>
> Best regards,
--
Hamza
prev parent reply other threads:[~2023-10-18 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 18:45 [PATCH] drm/amd/display: Respect CONFIG_FRAME_WARN=0 in DML2 Nathan Chancellor
2023-10-18 19:06 ` Hamza Mahfooz [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=263305cf-bedd-4419-a136-cecffd0eac89@amd.com \
--to=hamza.mahfooz@amd.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=nathan@kernel.org \
--cc=patches@lists.linux.dev \
--cc=sunpeng.li@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