From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Kees Cook <kees@kernel.org>
Cc: "Amit Dhingra" <mechanicalamit@gmail.com>,
"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, linux-hardening@vger.kernel.org
Subject: Re: linux-next-20251029 - build error in amdgpu
Date: Sat, 08 Nov 2025 10:10:16 -0500 [thread overview]
Message-ID: <357890.1762614616@turing-police> (raw)
In-Reply-To: <A9C2FED1-EFBF-48AD-A3C8-41DDD16F8AA1@kernel.org>
On Thu, 06 Nov 2025 06:02:23 -0800, Kees Cook said:
> Randstruct requires designated initializers, though I thought the macro
> turned that on universally, so the fact that the error is only present with
> randstruct seems like a separate bug.
Yeah, that's why I cc'ed you - looked to me like randstruct was doing something
weird...
\0AA1@kern
prev parent reply other threads:[~2025-11-10 9:25 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
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 [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=357890.1762614616@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=kees@kernel.org \
--cc=linux-hardening@vger.kernel.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.