linux-kernel - Re: [PATCH v3 0/6] rust: add `register!` macro

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: <DFYL8QGPXY92.3NPF5MTDSUZNE@kernel.org>
Date: Mon, 26 Jan 2026 15:24:52 +0100
From: "Danilo Krummrich" <dakr@...nel.org>
To: "Miguel Ojeda" <miguel.ojeda.sandonis@...il.com>
Cc: "Alexandre Courbot" <acourbot@...dia.com>, "Alice Ryhl"
 <aliceryhl@...gle.com>, "Daniel Almeida" <daniel.almeida@...labora.com>,
 "Miguel Ojeda" <ojeda@...nel.org>, "Boqun Feng" <boqun.feng@...il.com>,
 "Gary Guo" <gary@...yguo.net>, Björn Roy Baron
 <bjorn3_gh@...tonmail.com>, "Benno Lossin" <lossin@...nel.org>, "Andreas
 Hindborg" <a.hindborg@...nel.org>, "Trevor Gross" <tmgross@...ch.edu>,
 "Yury Norov" <yury.norov@...il.com>, "John Hubbard" <jhubbard@...dia.com>,
 "Alistair Popple" <apopple@...dia.com>, "Joel Fernandes"
 <joelagnelf@...dia.com>, "Timur Tabi" <ttabi@...dia.com>, "Edwin Peer"
 <epeer@...dia.com>, "Eliot Courtney" <ecourtney@...dia.com>, "Dirk Behme"
 <dirk.behme@...bosch.com>, "Steven Price" <steven.price@....com>,
 <rust-for-linux@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 0/6] rust: add `register!` macro

On Mon Jan 26, 2026 at 2:56 PM CET, Miguel Ojeda wrote:
> On Mon, Jan 26, 2026 at 2:29 PM Alexandre Courbot <acourbot@...dia.com> wrote:
>>
>> This patchset is based on `driver-core-next`.
>
> I think in the end you wanted to pick this through driver-core in this
> cycle, right?

Yes, if the series is ready until -rc8.

> I have sent Acked-by's for that, I hope it helps.

Thanks!

>> Note that it also need `rust-fixes` to avoid an `unused_unsafe` warning.
>
> That sounds fine, i.e. -next has it and Linus will have it before the
> merge window (unless you want to get rid of the warnings in your own
> branch).

Exactly, having this warning in the driver-core tree intermediately is fine with
me.

- Danilo