From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alex Deucher <alexdeucher@gmail.com>, Dave Airlie <airlied@redhat.com>
Cc: Qingqing Zhuo <Qingqing.Zhuo@amd.com>,
Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>,
Roman Li <roman.li@amd.com>,
DRI <dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Alex Deucher <alexander.deucher@amd.com>
Subject: Re: linux-next: build failure after merge of the amdgpu tree
Date: Tue, 24 Oct 2023 11:59:03 +1100 [thread overview]
Message-ID: <20231024115903.2d73440c@canb.auug.org.au> (raw)
In-Reply-To: <20231019120618.71424848@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]
Hi all,
On Thu, 19 Oct 2023 12:06:18 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> On Tue, 10 Oct 2023 12:43:57 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > After merging the amdgpu tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/display_mode_core.c: In function 'dml_core_mode_support':
> > drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/display_mode_core.c:8229:1: error: the frame size of 2736 bytes is larger than 2048 bytes [-Werror=frame-larger-than=]
> > 8229 | } // dml_core_mode_support
> > | ^
> > cc1: all warnings being treated as errors
> >
> > Caused by commit
> >
> > 7966f319c66d ("drm/amd/display: Introduce DML2")
> >
> > (or maybe something later that changed storage size).
> >
> > I have used the amdgpu tree from next-20231009 for today.
>
> This build failure now (presumably) exists in the drm tree. I am still
> applying the 2 patches from Rodrigo to my tree as a work around.
>
> I would have expected that this was fixed in the amdgpu tree before
> Dave was asked to merge it ...
Any progress here? I am still applying the 2 patches.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-10-24 0:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231010124357.5251e100@canb.auug.org.au>
2023-10-19 1:06 ` linux-next: build failure after merge of the amdgpu tree Stephen Rothwell
2023-10-24 0:59 ` Stephen Rothwell [this message]
2023-10-24 12:57 ` Alex Deucher
2023-10-24 19:52 ` Alex Deucher
2023-10-24 21:47 ` Stephen Rothwell
2024-08-19 1:56 Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2023-05-19 0:06 Stephen Rothwell
2023-05-19 3:10 ` James Zhu
2023-05-19 13:38 ` Alex Deucher
[not found] <20220307111342.105ce204@canb.auug.org.au>
[not found] ` <YiYC2fQgf7d/QPSM@sirena.org.uk>
2022-03-08 11:15 ` Noralf Trønnes
2021-12-03 1:11 Stephen Rothwell
2021-09-17 0:57 Stephen Rothwell
2021-07-28 12:34 Mark Brown
2021-02-05 2:12 Stephen Rothwell
[not found] <20200612102552.2d573ebb@canb.auug.org.au>
2020-06-26 1:47 ` Stephen Rothwell
[not found] <20190626212212.25b41df4@canb.auug.org.au>
2019-06-27 3:35 ` Stephen Rothwell
2019-06-27 14:18 ` Alex Deucher
2019-06-27 22:01 ` 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=20231024115903.2d73440c@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Qingqing.Zhuo@amd.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=airlied@redhat.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=roman.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