From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Amit Dhingra <mechanicalamit@gmail.com>
Cc: "Timur Kristóf" <timur.kristof@gmail.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Leo Li" <sunpeng.li@amd.com>, "David Airlie" <airlied@gmail.com>,
"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
linux-kernel@vger.kernel.org
Subject: Re: linux-next-20251029 - build error in amdgpu
Date: Wed, 05 Nov 2025 22:31:52 -0500 [thread overview]
Message-ID: <106367.1762399912@turing-police> (raw)
In-Reply-To: <CAO=gReERBacxH6SjLrcCNcStiAzMosR=aW5D4W925CJ_yjzbhA@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 407 bytes --]
On Wed, 05 Nov 2025 19:24:22 -0800, Amit Dhingra said:
> On Thu, Nov 06, 2025 at 03:40:52AM +0100, Timur Kristóf wrote:
> The patch above defining all fields seems to fix the error.
The bigger question is whether that patch merely papers over a bug in the gcc
plugin. Basically, why does the struct being one layout compile cleanly, but
throws an error if the layout is randomized...
\0m>
\0\0\0\0
next prev parent reply other threads:[~2025-11-06 13:41 UTC|newest]
Thread overview: 14+ 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
2025-11-02 0:59 ` Valdis Klētnieks
2025-11-02 9:27 ` Timur Kristóf
2025-11-06 2:34 ` Amit Dhingra
2025-11-06 2:40 ` Timur Kristóf
2025-11-06 3:24 ` Amit Dhingra
2025-11-06 3:29 ` Timur Kristóf
2025-11-06 3:32 ` Amit Dhingra
2025-11-06 3:31 ` Valdis Klētnieks [this message]
2025-11-06 3:18 ` Valdis Klētnieks
2025-11-06 14:02 ` Kees Cook
2025-11-06 23:49 ` Bill Wendling
2025-11-08 15:10 ` Valdis Klētnieks
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=106367.1762399912@turing-police \
--to=valdis.kletnieks@vt.edu \
--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=mechanicalamit@gmail.com \
--cc=sunpeng.li@amd.com \
--cc=timur.kristof@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.