linux-kernel - Re: [PATCH 1/3] gpu: nova-core: remove imports available via prelude

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] [day] [month] [year] [list]

Message-ID: <CANiq72mo+RpsTxZm7vEOBd+JQ7DJ65JE_q+H2oa57MeyyaHeqg@mail.gmail.com>
Date: Tue, 27 Jan 2026 12:44:02 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Danilo Krummrich <dakr@...nel.org>, Gary Guo <gary@...yguo.net>, 
	Nathan Chancellor <nathan@...nel.org>, Andreas Hindborg <a.hindborg@...nel.org>
Cc: Miguel Ojeda <ojeda@...nel.org>, Boqun Feng <boqun.feng@...il.com>, 
	Björn Roy Baron <bjorn3_gh@...tonmail.com>, 
	Benno Lossin <lossin@...nel.org>, Alice Ryhl <aliceryhl@...gle.com>, 
	Trevor Gross <tmgross@...ch.edu>, Alexandre Courbot <acourbot@...dia.com>, 
	David Airlie <airlied@...il.com>, Simona Vetter <simona@...ll.ch>, 
	Daniel del Castillo <delcastillodelarosadaniel@...il.com>, 
	Joel Fernandes <joelagnelf@...dia.com>, John Hubbard <jhubbard@...dia.com>, 
	Alistair Popple <apopple@...dia.com>, Lyude Paul <lyude@...hat.com>, Timur Tabi <ttabi@...dia.com>, 
	Shankari Anand <shankari.ak0208@...il.com>, rust-for-linux@...r.kernel.org, 
	nouveau@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] gpu: nova-core: remove imports available via prelude

On Tue, Jan 27, 2026 at 12:30 PM Danilo Krummrich <dakr@...nel.org> wrote:
>
> I just checked and there shouldn't be any conflicts, so if you want to pick this
> one up as well, please do. :)
>
> Acked-by: Danilo Krummrich <dakr@...nel.org>

Will, do thanks!

> Given that klint can do quite some convinient extra checks, should we consider
> making it an optional part of the build? Similar to what we do with clippy?

Yeah, that is the goal (e.g. `KLINT=1` or similar eventually).

But if someone wants to run it, it is already possible, IIUC Andreas
already did the other day.

To make things easier for developers/maintainers, I asked Nathan the
other day if we could have them in the LLVM+Rust kernel.org
toolchains, and he was supportive on adding it there when Gary is
ready, so it may be straightforward to set up in CIs! :)

(And later on, ideally, even on linux-next when we things are more settled)

Cheers,
Miguel