From: "Timur Kristóf" <timur.kristof@gmail.com>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>,
"Alex Deucher" <alexander.deucher@amd.com>
Cc: Leo Li <sunpeng.li@amd.com>, David Airlie <airlied@gmail.com>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: linux-next-20251029 - build error in amdgpu
Date: Thu, 30 Oct 2025 19:05:30 +0100 [thread overview]
Message-ID: <32ed124e9d603cad950c4836c7a14a3ba8bc2068.camel@gmail.com> (raw)
In-Reply-To: <1043551.1761844832@turing-police>
On Thu, 2025-10-30 at 13:20 -0400, Valdis Klētnieks wrote:
> Hit this error while building next-20251029 with W=1 and gcc (GCC)
> 15.2.1 20251022 (Red Hat 15.2.1-3
Hi,
Can you say how to reproduce that?
I use the same version of GCC but it hasn't given me any warning or
error for that patch.
Thanks & best regards,
Timur
>
> CC [M]
> drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dce_stream_encoder.o
> drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dce_stream_encoder.c:157
> 1:69: error: positional initialization of field in 'struct' declared
> with 'designated_init' attribute [-Werror=designated-init]
> 1571 | static const struct stream_encoder_funcs
> dce110_an_str_enc_funcs = {0};
>
> |
> ^
> drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dce_stream_encoder.c:157
> 1:69: note: (near initialization for 'dce110_an_str_enc_funcs')
> cc1: some warnings being treated as errors
>
> Caused by:
> commit deb072d241c906ae378bc88ff91dfcdc34ebe71a
> Author: Timur Krist?f <timur.kristof@gmail.com>
> Date: Fri Sep 26 20:01:51 2025 +0200
>
> drm/amd/display: Implement DCE analog stream encoders
>
>
> > > > > > > > >
prev parent reply other threads:[~2025-10-30 18:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 17:20 linux-next-20251029 - build error in amdgpu Valdis Klētnieks
2025-10-30 18:05 ` Timur Kristóf [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=32ed124e9d603cad950c4836c7a14a3ba8bc2068.camel@gmail.com \
--to=timur.kristof@gmail.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sunpeng.li@amd.com \
--cc=valdis.kletnieks@vt.edu \
/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;
as well as URLs for NNTP newsgroup(s).