linux-kernel - Re: [PATCH v6 3/4] gpu: nova-core: make Architecture behave as a u8 type

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <a8cc96d5ae80a256b9e0101acb1d1b38169d21b4.camel@nvidia.com>
Date: Sat, 8 Nov 2025 17:27:14 +0000
From: Timur Tabi <ttabi@...dia.com>
To: Alexandre Courbot <acourbot@...dia.com>, "dakr@...nel.org"
	<dakr@...nel.org>, John Hubbard <jhubbard@...dia.com>
CC: "lossin@...nel.org" <lossin@...nel.org>, "a.hindborg@...nel.org"
	<a.hindborg@...nel.org>, "boqun.feng@...il.com" <boqun.feng@...il.com>, Zhi
 Wang <zhiw@...dia.com>, "simona@...ll.ch" <simona@...ll.ch>,
	"tmgross@...ch.edu" <tmgross@...ch.edu>, "alex.gaynor@...il.com"
	<alex.gaynor@...il.com>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, "ojeda@...nel.org" <ojeda@...nel.org>,
	"nouveau@...ts.freedesktop.org" <nouveau@...ts.freedesktop.org>,
	"rust-for-linux@...r.kernel.org" <rust-for-linux@...r.kernel.org>,
	"nouveau-bounces@...ts.freedesktop.org"
	<nouveau-bounces@...ts.freedesktop.org>, "bjorn3_gh@...tonmail.com"
	<bjorn3_gh@...tonmail.com>, Edwin Peer <epeer@...dia.com>, Joel Fernandes
	<joelagnelf@...dia.com>, "airlied@...il.com" <airlied@...il.com>,
	"aliceryhl@...gle.com" <aliceryhl@...gle.com>, "bhelgaas@...gle.com"
	<bhelgaas@...gle.com>, "gary@...yguo.net" <gary@...yguo.net>, Alistair Popple
	<apopple@...dia.com>
Subject: Re: [PATCH v6 3/4] gpu: nova-core: make Architecture behave as a u8
 type

On Sat, 2025-11-08 at 20:45 +0900, Alexandre Courbot wrote:
> To be precise, we need to supply this because of a shortcoming in the
> `register`` macro: it doesn't support read-only registers yet, and write
> support requires a `Default` implementation for its fields. This is
> subject to be fixed in the future but for now we need this little
> workaround.

This definitely feels like something that needs a TODO comment.