From: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>
To: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>,
Roman Li <roman.li@amd.com>,
Qingqing Zhuo <Qingqing.Zhuo@amd.com>,
Alex Deucher <alexander.deucher@amd.com>
Cc: "Harry Wentland" <harry.wentland@amd.com>,
"Leo Li" <sunpeng.li@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Pan, Xinhui" <Xinhui.Pan@amd.com>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
"linux-kernel@vger.kernel.orgLinus Torvalds"
<torvalds@linux-foundation.org>,
regressions@lists.linux.dev
Subject: mainline build failure due to 7966f319c66d ("drm/amd/display: Introduce DML2")
Date: Thu, 2 Nov 2023 09:32:08 +0000 [thread overview]
Message-ID: <ZUNsmJGbYwgPaUpY@debian> (raw)
Hi All,
The latest mainline kernel branch fails to build x86_64 allmodconfig
with the error:
drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/display_mode_core.c: In function 'dml_prefetch_check':
drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/display_mode_core.c:6707:1: error: the frame size of 2056 bytes is larger than 2048 bytes [-Werror=frame-larger-than=]
6707 | }
| ^
git bisect pointed to 7966f319c66d ("drm/amd/display: Introduce DML2")
I will be happy to test any patch or provide any extra log if needed.
#regzbot introduced: 7966f319c66d9468623c6a6a017ecbc0dd79be75
--
Regards
Sudip
next reply other threads:[~2023-11-02 9:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 9:32 Sudip Mukherjee (Codethink) [this message]
2023-11-02 16:52 ` mainline build failure due to 7966f319c66d ("drm/amd/display: Introduce DML2") Alex Deucher
2023-11-02 17:07 ` Sudip Mukherjee
2023-11-02 22:53 ` Alex Deucher
2023-11-04 9:42 ` Sudip Mukherjee
2023-11-12 11:23 ` Linux regression tracking #update (Thorsten Leemhuis)
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=ZUNsmJGbYwgPaUpY@debian \
--to=sudipm.mukherjee@gmail.com \
--cc=Qingqing.Zhuo@amd.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=roman.li@amd.com \
--cc=sunpeng.li@amd.com \
--cc=torvalds@linux-foundation.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