linux-kernel - Re: [PATCH v3 0/3] rust: Build PHY device tables by using module_device

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: <CANiq72=Cbvrcwqt6PQHwwDVTx1vnVnQ7JBzzXk+K-7Va_OVHEQ@mail.gmail.com>
Date: Tue, 8 Jul 2025 20:47:13 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Danilo Krummrich <dakr@...nel.org>
Cc: FUJITA Tomonori <fujita.tomonori@...il.com>, kuba@...nel.org, gregkh@...uxfoundation.org, 
	robh@...nel.org, saravanak@...gle.com, alex.gaynor@...il.com, 
	ojeda@...nel.org, rafael@...nel.org, a.hindborg@...nel.org, 
	aliceryhl@...gle.com, bhelgaas@...gle.com, bjorn3_gh@...tonmail.com, 
	boqun.feng@...il.com, david.m.ertman@...el.com, devicetree@...r.kernel.org, 
	gary@...yguo.net, ira.weiny@...el.com, kwilczynski@...nel.org, 
	leon@...nel.org, linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org, 
	lossin@...nel.org, netdev@...r.kernel.org, rust-for-linux@...r.kernel.org, 
	tmgross@...ch.edu
Subject: Re: [PATCH v3 0/3] rust: Build PHY device tables by using
 module_device_table macro

On Tue, Jul 8, 2025 at 2:48 PM Danilo Krummrich <dakr@...nel.org> wrote:
>
> Had a brief look.
>
> There will be two trivial conflicts with the driver-core tree, which fixed up
> some of the safety comments you modify in this series as well.
>
> The other way around, there is one trivial conflict with Tamir patch in the rust
> tree fixing up an `as _` cast.
>
> So, either way works fine.

Thanks Danilo -- ditto. Even netdev could make sense as you said.

Since it touched several subsystems and it is based on rust-next, I am
happy to do so, but driver-core makes sense given that is the main
change after all.

So if I don't see you picking it, I will eventually do it.

Cheers,
Miguel