From: Thierry Reding <thierry.reding@kernel.org>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: DRI <dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the kthread tree
Date: Tue, 28 Apr 2026 14:56:53 +0200 [thread overview]
Message-ID: <20260428125654.3911280-1-thierry.reding@kernel.org> (raw)
Hi all,
After merging the amdgpu tree, today's linux-next build (arm64 allyesconfig)
failed like this:
/srv/kbuild/next/linux.git/drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn21/display_mode_vba_21.c: In function 'dml21_ModeSupportAndSystemConfigurationFull':
/srv/kbuild/next/linux.git/drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn21/display_mode_vba_21.c:5244:1: error: the frame size of 3232 bytes is larger than 3072 bytes [-Werror=frame-larger-than=]
5244 | }
| ^
cc1: all warnings being treated as errors
make[7]: *** [/srv/kbuild/next/linux.git/scripts/Makefile.build:289: drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn21/display_mode_vba_21.o] Error 1
make[7]: *** Waiting for unfinished jobs....
/srv/kbuild/next/linux.git/drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn30/display_mode_vba_30.c: In function 'dml30_ModeSupportAndSystemConfigurationFull':
/srv/kbuild/next/linux.git/drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn30/display_mode_vba_30.c:4961:1: error: the frame size of 3360 bytes is larger than 3072 bytes [-Werror=frame-larger-than=]
4961 | }
| ^
cc1: all warnings being treated as errors
make[7]: *** [/srv/kbuild/next/linux.git/scripts/Makefile.build:289: drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn30/display_mode_vba_30.o] Error 1
/srv/kbuild/next/linux.git/drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn32/display_mode_vba_32.c: In function 'dml32_ModeSupportAndSystemConfigurationFull':
/srv/kbuild/next/linux.git/drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn32/display_mode_vba_32.c:3762:1: error: the frame size of 3968 bytes is larger than 3072 bytes [-Werror=frame-larger-than=]
3762 | } // ModeSupportAndSystemConfigurationFull
| ^
cc1: all warnings being treated as errors
It's not clear to me what commit caused this, and looking at the mailing
lists it seems like this may have existed for a while and for different
configurations. I don't know if there any plans to try and fix this.
Thierry
next reply other threads:[~2026-04-28 12:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 12:56 Thierry Reding [this message]
2026-04-28 12:58 ` Alex Deucher
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=20260428125654.3911280-1-thierry.reding@kernel.org \
--to=thierry.reding@kernel.org \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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
all inboxes | Powered by JetHome®